Asset loading system

ABSTRACT

An identifier associated with one or more assets is obtained in response to a reader component reading a tag associated with one or more assets as the one or more assets traverse a conveyor apparatus. At least partially in response to the obtaining of the identifier, a storage unit of a plurality of storage units is caused to automatically rotate to a loading location to receive the one or more assets.

BACKGROUND

Before an asset (e.g., a package or parcel) reaches a final deliverydestination, it typically goes through various sorting operations. Forinstance, after a package has been dropped off at a carrier store for adelivery request, it may be routed to a sorting facility where thepackage traverses various different conveyor belt assemblies in thesorting facility based on information associated with the package (e.g.,size of package, destination address, weight, etc.). After traversal ofthe package through the sorting center, the package may be loaded into alogistics vehicle for delivery to the final delivery destination ordelivery to the next sorting phase operation.

Typical asset loading system technologies in the sorting and othercontexts include a conveyor belt assembly. These conveyor beltassemblies may include a belt that is generally formed and/or extendsaround at least two driving wheels such that by rotation of the drivingwheels, the conveyor belt surface may move an asset in a linear fashion.This may allow the asset to be picked and placed in a tray or othershelving location in preparation for delivery. However, these conveyorbelt assembly technologies, shelving location technologies, and othercomponents of asset loading systems are static and include limitedfunctionality, as described in more detail herein.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used in isolation as an aid in determining the scope of the claimedsubject matter. Further, alternative or additional embodiments existother than those described in this summary section.

Some embodiments are directed to a system that includes a plurality ofstorage units that are configured to receive one or more assetsassociated with performing one or more shipment operations. The systemmay also include a conveyor apparatus that is configured to relay theone or more assets. A first asset of the one or more assets may beconfigured to be picked from the conveyor apparatus and loaded onto atleast one storage unit of the plurality of storage units for the one ormore shipment operations. The conveyor apparatus can be communicativelycoupled to the plurality of storage units or communicatively coupled toone or more computing devices associated with the plurality of storageunits. The at least one storage unit of the plurality of storage unitscan be configured to automatically rotate to a loading location at leastpartially in response to receiving a communication from the conveyorapparatus or the one or more computing devices indicating an identifierassociated with the first asset.

Some embodiments are directed to a conveyor apparatus that includes arotating component that is configured to cause movement of one or moreassets for loading the one or more assets into one or more storageunits. The conveyor apparatus can further include a reader componentconfigured to obtain an identifier associated with the one or moreassets. The conveyor apparatus can further include a transmittingcomponent configured to transmit, over a computer network, theidentifier obtained by the reader component to the one or more storageunits or one or more computing devices associated with the one or morestorage units such that the one or more storage units are configured torotate to a loading location for the loading of the one or more assetsin response to receiving the identifier.

Some embodiments are directed to a computer-implemented method thatincludes the following operations. An identifier associated with one ormore assets can be obtained in response to a reader component reading atag associated with one or more assets as the one or more assetstraverse a conveyor apparatus. At least partially in response to theobtaining of the identifier, a storage unit of a plurality of storageunits can be caused to automatically rotate to a loading location toreceive the one or more assets.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described the disclosure in general terms, reference willnow be made to the accompanying drawings, which are not necessarilydrawn to scale, and wherein:

FIG. 1 is a schematic diagram of an example computing environment inwhich aspects of the present disclosure are employed, according to someembodiments.

FIG. 2 is a schematic diagram of one or more logistics server(s) inwhich aspects of the present disclosure are employed, according to someembodiments.

FIG. 3 is a schematic diagram of a computing entity in which aspects ofthe present disclosure are employed, according to some embodiments.

FIG. 4A is a schematic diagram of an environment illustrating how one ormore assets are loaded into storage units inside a logistics vehicle,according to some embodiments.

FIG. 4B is a more detailed view of the reading component of FIG. 4A,according to some embodiments.

FIG. 5 is a schematic diagram of an environment illustrating how one ormore assets are loaded into storage units inside a logistics vehicle,according to some embodiments.

FIG. 6 is a schematic diagram of an environment illustrating how one ormore assets are loaded into storage units that are outside of alogistics vehicle, according to some embodiments.

FIG. 7 is a schematic diagram of an environment illustrating how one ormore assets are loaded into storage units that are outside of alogistics vehicle, according to some embodiments.

FIG. 8A is a schematic diagram of an environment illustrating how one ormore assets are loaded into storage units that are configured to beadjusted into a U-shape, according to some embodiments.

FIG. 8B is a schematic diagram illustrating how the individual storageunits of FIG. 8A may be oriented and adjusted in order to contribute tothe overall U-shape (or any other suitable shape) of the storage units,according to some embodiments.

FIG. 8C is a top view of the storage units of FIG. 8B illustrating howindividual storage units may be oriented and adjusted in order tocontribute to the overall U-shape (or any other suitable shape) of thestorage units.

FIG. 8D is a rear view of the storage units of FIG. 8B illustrating howindividual storage units may be oriented and adjusted in order tocontribute to the overall U-shape (or any other suitable shape) of thestorage units, according to some embodiments.

FIG. 9 is a schematic diagram of an environment illustrating how one ormore assets are loaded into storage units that are configured to beadjusted into a semi-circle shape, according to some embodiments.

FIG. 10 is a schematic diagram of an environment illustrating how one ormore buffer shelves are used for loading one or more assets, accordingto some embodiments.

FIG. 11 is a block diagram of an example queue data structureillustrating how storage units can be rotated or shifted to a loadinglocation, according to some embodiments.

FIG. 12 is a flow diagram of an example process for causing a storageunit to rotate to a loading location to store one or more assets,according to some embodiments.

DETAILED DESCRIPTION OF THE INVENTION

The present disclosure will now be described more fully hereinafter withreference to the accompanying drawings, in which some, but not allembodiments of the disclosure are shown. Indeed, the disclosure may beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Rather, these embodiments areprovided so that this disclosure will satisfy applicable legalrequirements. Like numbers refer to like elements throughout.

I. Overview

As described above, existing technologies are static and include limitedfunctionality. For example, existing conveyor belt assembly technologiesuse simple logic or computer-implemented conditional rules toactivate/deactivate rotation of the belt or change speeds of the belt.However, no conveyor belt technologies are currently able to performmore dynamic operations, such as communicatively couple (e.g., via awireless computer network) to other components to perform asset loadingfunctionality. Various embodiments of the present disclosure improveconveyor belt technologies by communicatively coupling with othercomponents, such as one or more logistics servers (e.g., cloud computingnodes, servers, etc.), logistics vehicles, and/or storage units thatreceive assets. In various instances, this communicative coupling allowsfor even further functionality that improves existing technologies. Forexample, a conveyor apparatus may include a reader component that readseach tag coupled to an asset as each asset traverses past the readercomponent and sends data located in the tag, over a computer network, toone or more logistics servers, logistics vehicles, and/or storage unitsso that the one or more storage units can automatically rotate to aloading location (e.g., the back of a vehicle where an operator isstanding) responsive to receiving and analyzing the tag data for eachasset. In this way, for example, embodiments can anticipate a sequenceof assets as the assets move, on a conveyor apparatus, towards a loadingoperator's position and responsively and automatically shift or rotatethe storage units in advance such that by the time each asset is pickedfrom the conveyor apparatus, the corresponding storage unit is alreadypositioned to the loading location. A particular storage unit may beneeded for various reasons or asset attributes (e.g., asset size,destination location, dimensions, etc.). For example, various assets maybe grouped together by zip code, destination location, geocode, or thelike so that when the assets are unloaded, each asset can be physicallynear each other in shelving units. Accordingly, each asset may have acorresponding storage unit it will be stored to and the correspondingstorage units may automatically rotate to a loading location based onasset attributes or identifiers and the sequence it is read in by thereading component.

Existing shelving unit technologies either contain no computer logic forautomated movement or move based on manual user selections. For example,existing shelving unit technologies may include a physical label thathuman operators read so that they can associate information on an assetwith the label. This may require arduous labor by the human operatorsuch as manually rotating or otherwise moving shelving units so that theoperator can place the asset in the correct shelving location. This mayfurther require the human operator to extensively orient herself orotherwise move in various locations to get to the correct shelvinglocation. In another example, shelving unit technologies may require theuser to manually input information on a computer. For instance, ashelving unit or other device may include a key pad that prompts a userto manually type in asset data. After the user inputs this information,the user may then have to manually find the correct location. Variousembodiments improve these existing shelving unit technologies byautomatically rotating particular storage units to a loading location atleast partially in response to receiving a communication from a conveyorapparatus or one or more other computing devices (e.g., a logisticsserver). This communication may include information, such as destinationaddress information or other identifiers on an asset, which is used bythe storage unit system to locate the particular storage unit and rotateit to the particular loading location so that the user or operator caneasily place the asset in the unit without orienting or otherwisecausing unnecessary movement, either with respect to the storage unitsthemselves or orienting her body.

Additional embodiments described herein improve existing shelving unittechnologies by including storage units that comprise one or morefastening mechanisms or components that cause a fixed axis to be formedbetween an anterior or front portion of the storage units (e.g., but nota back portion of the storage units) such that each storage unit can becoupled together and swing or pivot about the axis in an inward oroutward fashion, as described, for example, with respect to FIGS. 8Athrough 8D. In this way, a plurality of storage units together areflexible such that they can take on a particular orientation or shape(e.g., a U-shape or semicircle) for access during asset loading and forbeing able to fit within a logistics vehicle.

Generally, existing asset loading system technologies require extensivemanual human input, with limited functionality as described herein.Various embodiments of the present disclosure improve these existingasset loading system technologies by performing new functionality thatno asset loading technologies or humans have performed before (e.g., viathe new conveyor apparatus functionality or storage unit functionalitydescribed above). For instance, some embodiments improve thesetechnologies by automating various processes (e.g., automaticallyrotating a storage unit to a loading location) based on one or morerules (e.g., receiving an identifier identifying asset attributes, suchas destination and size). As described herein, humans themselves andstatic technology, especially in the shipping industry, havehistorically required extensive manual intervention to load assets.However, both conventional techniques and existing technology in theshipping industry have not performed the new and improved functionalityas described herein. For example, each of the FIGS. 4A through 12describe functionality that improves existing asset loading systemtechnology and conventional techniques used in the shipping industry.

In is understood that although this overview section describes variousimprovements to conventional solutions and technologies, these are byway of example only. As such, other improvements are described below orwill become evident through description of various embodiments. Thisoverview is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This overview is not intended to: identify key features oressential features of the claimed subject matter, key improvements, noris it intended to be used in isolation as an aid in determining thescope of the claimed subject matter.

II. Apparatuses, Methods, and Systems

Embodiments of the present disclosure may be implemented in variousways, including as apparatuses that comprise articles of manufacture. Anapparatus may include a non-transitory computer-readable storage mediumstoring applications, programs, program modules, scripts, source code,program code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like (also referred toherein as executable instructions, instructions for execution, programcode, and/or similar terms used herein interchangeably). Suchnon-transitory computer-readable storage media include allcomputer-readable media (including volatile and non-volatile media).

In one embodiment, a non-volatile computer-readable storage medium mayinclude a floppy disk, flexible disk, hard disk, solid-state storage(SSS) (e.g., a solid state drive (SSD), solid state card (SSC), solidstate module (SSM)), enterprise flash drive, magnetic tape, or any othernon-transitory magnetic medium, and/or the like. A non-volatilecomputer-readable storage medium may also include a punch card, papertape, optical mark sheet (or any other physical medium with patterns ofholes or other optically recognizable indicia), compact disc read onlymemory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc(DVD), Blu-ray disc (BD), any other non-transitory optical medium,and/or the like. Such a non-volatile computer-readable storage mediummay also include read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), flash memory (e.g.,Serial, NAND, NOR, and/or the like), multimedia memory cards (MMC),secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF)cards, Memory Sticks, and/or the like. Further, a non-volatilecomputer-readable storage medium may also include conductive-bridgingrandom access memory (CBRAM), phase-change random access memory (PRAM),ferroelectric random-access memory (FeRAM), non-volatile random-accessmemory (NVRAM), magnetoresistive random-access memory (MRAM), resistiverandom-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory(SONOS), floating junction gate random access memory (FJG RAM),Millipede memory, racetrack memory, and/or the like.

In one embodiment, a volatile computer-readable storage medium mayinclude random access memory (RAM), dynamic random access memory (DRAM),static random access memory (SRAM), fast page mode dynamic random accessmemory (FPM DRAM), extended data-out dynamic random access memory (EDODRAM), synchronous dynamic random access memory (SDRAM), doubleinformation/data rate synchronous dynamic random access memory (DDRSDRAM), double information/data rate type two synchronous dynamic randomaccess memory (DDR2 SDRAM), double information/data rate type threesynchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamicrandom access memory (RDRAM), Twin Transistor RAM (TTRAM), Thyristor RAM(T-RAM), Zero-capacitor (Z-RAM), Rambus in-line memory module (RIMM),dual in-line memory module (DIMM), single in-line memory module (SIMM),video random access memory (VRAM), cache memory (including variouslevels), flash memory, register memory, and/or the like. It will beappreciated that where embodiments are described to use acomputer-readable storage medium, other types of computer-readablestorage media may be substituted for or used in addition to thecomputer-readable storage media described above.

As should be appreciated, various embodiments of the present disclosuremay also be implemented as methods, apparatuses, systems, computingdevices/entities, computing entities, and/or the like. As such,embodiments of the present disclosure may take the form of an apparatus,system, computing device, computing entity, and/or the like executinginstructions stored on a computer-readable storage medium to performcertain steps or operations. However, embodiments of the presentdisclosure may also take the form of an entirely hardware embodimentperforming certain steps or operations.

Embodiments of the present disclosure are described below with referenceto block diagrams and flowchart illustrations. Thus, it should beunderstood that each block of the block diagrams and flowchartillustrations may be implemented in the form of a computer programproduct, an entirely hardware embodiment, a combination of hardware andcomputer program products, and/or apparatuses, systems, computingdevices/entities, computing entities, and/or the like carrying outinstructions, operations, steps, and similar words used interchangeably(e.g., the executable instructions, instructions for execution, programcode, and/or the like) on a computer-readable storage medium forexecution. For example, retrieval, loading, and execution of code may beperformed sequentially such that one instruction is retrieved, loaded,and executed at a time. In some exemplary embodiments, retrieval,loading, and/or execution may be performed in parallel such thatmultiple instructions are retrieved, loaded, and/or executed together.Thus, such embodiments can produce specifically-configured machinesperforming the steps or operations specified in the block diagrams andflowchart illustrations. Accordingly, the block diagrams and flowchartillustrations support various combinations of embodiments for performingthe specified instructions, operations, or steps.

III. Exemplary System Architecture

FIG. 1 is a schematic diagram of an example computing environment 100 inwhich aspects of the present disclosure are employed, according to someembodiments. As shown in FIG. 1, this particular computing environment100 includes one or more logistics vehicles 120, one or more logisticsservers 105, one or more computing entities 110 (e.g., a mobile device,such as a DIAD), one or more satellites (not shown), one or morenetworks 135, a plurality of storage units 123, and a conveyor apparatus125. Each of these components, entities, devices, systems, and similarwords used herein interchangeably may be in direct or indirectcommunication with, for example, one another over the same or differentwired and/or wireless networks. Additionally, while FIG. 1 illustratesthe various system entities as separate, standalone entities, thevarious embodiments are not limited to this particular architecture.

In various embodiments, the network(s) 135 represents or includes an IoT(internet of things) or IoE (internet of everything) network, which is anetwork of interconnected items (e.g., the storage units 123 and theconveyor apparatus 125) that are each provided with unique identifiers(e.g., UIDs) and computing logic so as to communicate or transfer datawith each other or other components. Such communication can happenwithout requiring human-to-human or human-to-computer interaction. Forexample, an IoT network may include the logistics vehicle 120, which isequipped with one or more sensors and transmitters in order to processand/or transmit sensor data over the network 135 to the logisticsserver(s) 105, the storage units 123, and/or the conveyor apparatus. Inthe context of an IoT network, a computer (not shown) within thelogistics vehicle 120 (or any of the other components) can be or includeone or more local processing devices (e.g., edge nodes) that are one ormore computing devices configured to store and process, over thenetwork(s) 135, either a subset or all of the received or respectivesets of data to the one or more remote computing devices (e.g., thecomputing entities 110 and/or the logistics server(s) 105) for analysis.

In some embodiments, the local processing device(s) described above is amesh or other network of microdata centers or edge nodes that processand store local data received from sensors coupled to the storage units123, conveyor apparatus 125, and/or the logistics vehicle 120 and pushor transmit some or all of the data to a cloud device or a corporatedata center that is or is included in the one or more logisticsserver(s) 105. In some embodiments, the local processing device(s)stores all of the data and only transmits selected (e.g., data thatmeets a threshold) or important data to the one or more logisticsservers 105. Accordingly, the non-important data or the data that is ina group that does not meet a threshold is not transmitted. For example,the conveyor apparatus 125 may interrogate a tag on a parcel to receivedata but only push a portion of the received data. Accordingly, onlyafter the condition or threshold has been met does the local processingdevice(s) transmit the data that meets or exceeds the threshold toremote computing devices such that the remote device(s) can takeresponsive actions, such as notify a user mobile device (e.g., computingentity 110) indicating the threshold has been met and/or cause amodification of data (e.g., consolidate entries of purchase orders). Thedata that does not meet or exceed the threshold is not transmitted inparticular embodiments. In various embodiments where the threshold orcondition is not met, daily or other time period reports areperiodically generated and transmitted from the local processingdevice(s) to the remote device(s) indicating all the data readingsgathered and processed at the local processing device(s). In someembodiments, the one or more local processing devices act as a buffer orgateway between the network(s) and a broader network, such as the one ormore networks 135. Accordingly, in these embodiments, the one or morelocal processing devices can be associated with one or more gatewaydevices that translate proprietary communication protocols into otherprotocols, such as internet protocols.

1. Exemplary Analysis Computing Entities

FIG. 2 provides a schematic of a logistics server(s) 105 according toparticular embodiments of the present disclosure. In general, the termscomputing entity, computer, entity, device, system, and/or similar wordsused herein interchangeably may refer to, for example, one or morecomputers, computing entities, desktops, mobile phones, tablets,phablets, notebooks, laptops, distributed systems, consoles inputterminals, servers or server networks, blades, gateways, switches,processing devices, processing entities, set-top boxes, relays, routers,network access points, base stations, cloud computing nodes, virtualmachines, virtual containers, the like, and/or any combination ofdevices or entities adapted to perform the functions, operations, and/orprocesses described herein. Such functions, operations, and/or processesmay include, for example, transmitting, receiving, operating on,processing, displaying, storing, determining, creating/generating,monitoring, evaluating, comparing, and/or similar terms used hereininterchangeably. In particular embodiments, these functions, operations,and/or processes can be performed on data, content, information/data,and/or similar terms used herein interchangeably.

As indicated, in particular embodiments, the logistics server(s) 105 mayalso include one or more communications interfaces 220 for communicatingwith various computing entities, such as by communicating data, content,information/data, and/or similar terms used herein interchangeably thatcan be transmitted, received, operated on, processed, displayed, stored,and/or the like.

As shown in FIG. 2, in particular embodiments, the logistics server(s)105 may include or be in communication with one or more processingelements 205 (also referred to as processors, processing circuitry,and/or similar terms used herein interchangeably) that communicate withother elements within the logistics server(s) 105 via a bus, forexample. As will be understood, the processing element 205 may beembodied in a number of different ways. For example, the processingelement 205 may be embodied as one or more complex programmable logicdevices (CPLDs), microprocessors, multi-core processors, co-processingentities, application-specific instruction-set processors (ASIPs),microcontrollers, and/or controllers. Further, the processing element205 may be embodied as one or more other processing devices orcircuitry. The term circuitry may refer to an entirely hardwareembodiment or a combination of hardware and computer program products.Thus, the processing element 205 may be embodied as integrated circuits,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), programmable logic arrays (PLAs), hardwareaccelerators, other circuitry, and/or the like. As will therefore beunderstood, the processing element 205 may be configured for aparticular use or configured to execute instructions stored in volatileor non-volatile media or otherwise accessible to the processing element205. As such, whether configured by hardware or computer programproducts, or by a combination thereof, the processing element 205 may becapable of performing steps or operations according to embodiments ofthe present disclosure when configured accordingly.

In particular embodiments, the logistics server(s) 105 may furtherinclude or be in communication with non-volatile media (also referred toas non-volatile storage, memory, memory storage, memory circuitry and/orsimilar terms used herein interchangeably). In particular embodiments,the non-volatile storage or memory may include one or more non-volatilestorage or memory media 210, including but not limited to hard disks,ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, MemorySticks, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipedememory, racetrack memory, and/or the like. As will be recognized, thenon-volatile storage or memory media may store databases (e.g.,parcel/item/shipment database), database instances, database managementsystems, data, applications, programs, program modules, scripts, sourcecode, object code, byte code, compiled code, interpreted code, machinecode, executable instructions, and/or the like. The term database,database instance, database management system, and/or similar terms usedherein interchangeably may refer to a collection of records orinformation/data that is stored in a computer-readable storage mediumusing one or more database models, such as a hierarchical databasemodel, network model, relational model, entity-relationship model,object model, document model, semantic model, graph model, and/or thelike.

In particular embodiments, the logistics server(s) 105 may furtherinclude or be in communication with volatile media (also referred to asvolatile storage, memory, memory storage, memory circuitry and/orsimilar terms used herein interchangeably). In particular embodiments,the volatile storage or memory may also include one or more volatilestorage or memory media 215, including but not limited to RAM, DRAM,SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM,RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory,register memory, and/or the like. As will be recognized, the volatilestorage or memory media may be used to store at least portions of thedatabases, database instances, database management systems, data,applications, programs, program modules, scripts, source code, objectcode, byte code, compiled code, interpreted code, machine code,executable instructions, and/or the like being executed by, for example,the processing element 205. Thus, the databases, database instances,database management systems, data, applications, programs, programmodules, scripts, source code, object code, byte code, compiled code,interpreted code, machine code, executable instructions, and/or the likemay be used to control certain aspects of the operation of the logisticsserver(s) 105 with the assistance of the processing element 205 andoperating system.

As indicated, in particular embodiments, the logistics server(s) 105 mayalso include one or more communications interfaces 220 for communicatingwith various computing entities, such as by communicatinginformation/data, content, information/data, and/or similar terms usedherein interchangeably that can be transmitted, received, operated on,processed, displayed, stored, and/or the like. Such communication may beexecuted using a wired information/data transmission protocol, such asfiber distributed information/data interface (FDDI), digital subscriberline (DSL), Ethernet, asynchronous transfer mode (ATM), frame relay,information/data over cable service interface specification (DOCSIS), orany other wired transmission protocol. Similarly, the logisticsserver(s) 105 may be configured to communicate via wireless externalcommunication networks using any of a variety of protocols, such asgeneral packet radio service (GPRS), Universal Mobile TelecommunicationsSystem (UMTS), Code Division Multiple Access 2000 (CDMA2000), CDMA20001× (1×RTT), Wideband Code Division Multiple Access (WCDMA), TimeDivision-Synchronous Code Division Multiple Access (TD-SCDMA), Long TermEvolution (LTE), Evolved Universal Terrestrial Radio Access Network(E-UTRAN), Evolution-Data Optimized (EVDO), High Speed Packet Access(HSPA), High-Speed Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi),Wi-Fi Direct, 802.16 (WiMAX), ultra wideband (UWB), infrared (IR)protocols, near field communication (NFC) protocols, Wibree, Bluetoothprotocols, wireless universal serial bus (USB) protocols, long range lowpower (LoRa), LTE Cat M1, NarrowBand IoT (NB IoT), and/or any otherwireless protocol.

Although not shown, the logistics server(s) 105 may include or be incommunication with one or more input elements, such as a keyboard input,a mouse input, a touch screen/display input, motion input, movementinput, audio input, pointing device input, joystick input, keypad input,and/or the like. The logistics server(s) 105 may also include or be incommunication with one or more output elements (not shown), such asaudio output, video output, screen/display output, motion output,movement output, and/or the like.

As will be appreciated, one or more of the logistics server(s)'s 105components may be located remotely from other logistics server(s) 105components, such as in a distributed system (e.g., a cloud computingsystem). Additionally or alternatively, the logistics server(s) 105 maybe represented among a plurality of logistics servers. For example, thelogistics server(s) 105 can be or be included in a cloud computingenvironment, which includes a network-based, distributed/data processingsystem that provides one or more cloud computing services. Further, acloud computing environment can include many computers, hundreds orthousands of them or more, disposed within one or more data centers andconfigured to share resources over the network(s) 135. Furthermore, oneor more of the components may be combined and additional componentsperforming functions described herein may be included in the logisticsserver(s) 105. Thus, the logistics server(s) 105 can be adapted toaccommodate a variety of needs and circumstances. As will be recognized,these architectures and descriptions are provided for exemplary purposesonly and are not limiting to the various embodiments.

2. Exemplary Computing Entities

Computing entities 110 may be configured for: reading tag data from anasset that traverses the conveyor apparatus and transmitting the data,causing automatic rotation of one of the storage units 123 to a loadinglocation, processing one or more shipping requests, monitoringshipments, and/or operation by a user (e.g., a vehicle operator,delivery personnel, customer, and/or the like). In some embodiments, acomputing entity 110 is embedded within or otherwise coupled to thestorage units 123, the logistics vehicle 120, and/or conveyor apparatus125 so that these components may perform their suitable functionality asdescribed herein. In certain embodiments, computing entities 110 may beembodied as handheld computing entities, such as mobile phones, tablets,personal digital assistants, and/or the like, that may be operated atleast in part based on user input received from a user via an inputmechanism. Moreover, computing entities 110 may be embodied as onboardvehicle computing entities, such as central vehicle electronic controlunits (ECUs), onboard multimedia system, and/or the like that may beoperated at least in part based on user input. Such onboard vehiclecomputing entities may be configured for autonomous and/or nearlyautonomous operation however, as they may be embodied as onboard controlsystems for autonomous or semi-autonomous vehicles, such as unmannedaerial vehicles (UAVs), robots, and/or the like. As a specific example,computing entities 110 may be utilized as onboard controllers for UAVsconfigured for picking-up and/or delivering packages to variouslocations, and accordingly such computing entities 110 may be configuredto monitor various inputs (e.g., from various sensors) and generatevarious outputs. It should be understood that various embodiments of thepresent disclosure may comprise a plurality of computing entities 110embodied in one or more forms (e.g., parcel security devices kiosks,mobile devices, watches, laptops, carrier personnel devices (e.g.,Delivery Information Acquisition Devices (DIAD)), etc.).

As will be recognized, a user may be an individual, a family, a company,an organization, an entity, a department within an organization, arepresentative of an organization and/or person, and/or the like—whetheror not associated with a carrier. In particular embodiments, a user mayoperate a computing entity 110 that may include one or more componentsthat are functionally similar to those of the logistics server(s) 105.FIG. 3 provides an illustrative schematic representative of a computingentity 110 that can be used in conjunction with embodiments of thepresent disclosure. In general, the terms device, system, computingentity, entity, and/or similar words used herein interchangeably mayrefer to, for example, one or more computers, computing entities,desktops, mobile phones, tablets, phablets, notebooks, laptops,distributed systems, vehicle multimedia systems, autonomous vehicleonboard control systems, watches, glasses, key fobs, radio frequencyidentification (RFID) tags/readers, ear pieces, scanners, imagingdevices/cameras (e.g., part of a multi-view image capture system),wristbands, kiosks, input terminals, servers or server networks, blades,gateways, switches, processing devices, processing entities, set-topboxes, relays, routers, network access points, base stations, the like,and/or any combination of devices or entities adapted to perform thefunctions, operations, and/or processes described herein. Computingentities 110 can be operated by various parties, including carrierpersonnel (sorters, operators, delivery drivers, network administrators,and/or the like). As shown in FIG. 3, the computing entity 110 caninclude an antenna 312, a transmitter 304 (e.g., radio), a receiver 306(e.g., radio), and a processing element 308 (e.g., CPLDs,microprocessors, multi-core processors, coprocessing entities, ASIPs,microcontrollers, and/or controllers) that provide signals to andreceive signals from the transmitter 304 and receiver 306, respectively.In some embodiments, the computing entity 110 includes one or moresensors 330 (e.g., a tag reader). In some embodiments, at least one ofthe computing entities 110 is coupled to the logistics vehicle 120. Theone or more sensors 330 can be one or more of: a pressure sensor, anaccelerometer, a gyroscope, a geolocation sensor (e.g., GPS sensor), aradar, a lidar, sonar, ultrasound, an object recognition camera, and anyother suitable sensor used to detect objects or obtain information in ageographical environment that the logistics vehicle 120 is within.

The signals provided to and received from the transmitter 304 and thereceiver 306, respectively, may include signaling information inaccordance with air interface standards of applicable wireless systems.In this regard, the computing entity 110 may be capable of operatingwith one or more air interface standards, communication protocols,modulation types, and access types. More particularly, the computingentity 110 may operate in accordance with any of a number of wirelesscommunication standards and protocols, such as those described abovewith regard to the logistics server(s) 105. In a particular embodiment,the computing entity 110 may operate in accordance with multiplewireless communication standards and protocols, such as UMTS, CDMA2000,1×RTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-FiDirect, WiMAX, UWB, IR, NFC, Bluetooth, USB, and/or the like. Similarly,the computing entity 110 may operate in accordance with multiple wiredcommunication standards and protocols, such as those described abovewith regard to the logistics server(s) 105 via a network interface 320.

Via these communication standards and protocols, the computing entity110 can communicate with various other entities using concepts such asUnstructured Supplementary Service information/data (USSD), ShortMessage Service (SMS), Multimedia Messaging Service (MMS), Dual-ToneMulti-Frequency Signaling (DTMF), and/or Subscriber Identity ModuleDialer (SIM dialer). The computing entity 110 can also download changes,add-ons, and updates, for instance, to its firmware, software (e.g.,including executable instructions, applications, program modules), andoperating system.

According to particular embodiments, the computing entity 110 mayinclude location determining aspects, devices, modules, functionalities,and/or similar words used herein interchangeably. For example, thecomputing entity 110 may include outdoor positioning aspects, such as alocation module adapted to acquire, for example, latitude, longitude,altitude, geocode, course, direction, heading, speed, universal time(UTC), date, and/or various other information/data. In particularembodiments, the location module can acquire information/data, sometimesknown as ephemeris information/data, by identifying the number ofsatellites in view and the relative positions of those satellites (e.g.,using global positioning systems (GPS)). The satellites may be a varietyof different satellites, including Low Earth Orbit (LEO) satellitesystems, Department of Defense (DOD) satellite systems, the EuropeanUnion Galileo positioning systems, the Chinese Compass navigationsystems, Indian Regional Navigational satellite systems, and/or thelike. This information/data can be collected using a variety ofcoordinate systems, such as the Decimal Degrees (DD); Degrees, Minutes,Seconds (DMS); Universal Transverse Mercator (UTM); Universal PolarStereographic (UPS) coordinate systems; and/or the like. Alternatively,the location information can be determined by triangulating thecomputing entity's 110 position in connection with a variety of othersystems, including cellular towers, Wi-Fi access points, and/or thelike. Similarly, the computing entity 110 may include indoor positioningaspects, such as a location module adapted to acquire, for example,latitude, longitude, altitude, geocode, course, direction, heading,speed, time, date, and/or various other information/data. Some of theindoor systems may use various position or location technologiesincluding RFID tags, indoor beacons or transmitters, Wi-Fi accesspoints, cellular towers, nearby computing devices/entities (e.g.,smartphones, laptops), and/or the like. For instance, such technologiesmay include the iBeacons, Gimbal proximity beacons, Bluetooth Low Energy(BLE) transmitters, NFC transmitters, and/or the like. These indoorpositioning aspects can be used in a variety of settings to determinethe location of someone or something to within inches or centimeters.

The computing entity 110 may also comprise a user interface (that caninclude a display 316 coupled to a processing element 308) and/or a userinput interface (coupled to a processing element 308). For example, theuser interface may be a user application, browser, user interface,and/or similar words used herein interchangeably executing on and/oraccessible via the computing entity 110 to interact with and/or causedisplay of information from the logistics server(s) 105, as describedherein. The user input interface can comprise any of a number of devicesor interfaces allowing the computing entity 110 to receiveinformation/data, such as a keypad 318 (hard or soft), a touch display,voice/speech or motion interfaces, or other input device. In embodimentsincluding a keypad 318, the keypad 318 can include (or cause display of)the conventional numeric (0-9) and related keys (#, *), and other keysused for operating the computing entity 110 and may include a full setof alphabetic keys or set of keys that may be activated to provide afull set of alphanumeric keys. In addition to providing input, the userinput interface can be used, for example, to activate or deactivatecertain functions, such as screen savers and/or sleep modes.

As shown in FIG. 3, the computing entity 110 may also include a camera,imaging device, and/or similar words used herein interchangeably 326(e.g., still-image camera, video camera, IoT enabled camera, IoT modulewith a low resolution camera, a wireless enabled MCU, and/or the like)configured to capture images. The computing entity 110 may be configuredto capture images via the onboard camera 326, and to store those imagingdevices/cameras locally, such as in the volatile memory 322 and/ornon-volatile memory 324. As discussed herein, the computing entity 110may be further configured to match the captured image data with relevantlocation and/or time information captured via the location determiningaspects to provide contextual information/data, such as a time-stamp,date-stamp, location-stamp, and/or the like to the image data reflectiveof the time, date, and/or location at which the image data was capturedvia the camera 326. The contextual data may be stored as a portion ofthe image (such that a visual representation of the image data includesthe contextual data) and/or may be stored as metadata (e.g., data thatdescribes other data, such as describing a payload) associated with theimage data that may be accessible to various computing entities 110.

The computing entity 110 may include other input mechanisms, such asscanners (e.g., barcode scanners), microphones, accelerometers, RFIDreaders (or Near-Field Communication (NFC) readers), and/or the likeconfigured to capture and store various information types for thecomputing entity 110. For example, a scanner may be used to captureparcel/item/shipment information/data from an item indicator disposed ona surface of a shipment or other item. In certain embodiments, thecomputing entity 110 may be configured to associate any captured inputinformation/data, for example, via the onboard processing element 308.For example, scan data captured via a scanner may be associated withimage data captured via the camera 326 such that the scan data isprovided as contextual data associated with the image data.

The computing entity 110 can also include volatile storage or memory 322and/or non-volatile storage or memory 324, which can be embedded and/ormay be removable. For example, the non-volatile memory may be ROM, PROM,EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks,CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory,racetrack memory, and/or the like. The volatile memory may be RAM, DRAM,SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM,RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory,register memory, and/or the like. The volatile and non-volatile storageor memory can store databases, database instances, database managementsystems, information/data, applications, programs, program modules,scripts, source code, object code, byte code, compiled code, interpretedcode, machine code, executable instructions, and/or the like toimplement the functions of the computing entity 110. As indicated, thismay include a user application that is resident on the entity oraccessible through a browser or other user interface for communicatingwith the logistics server(s) 105 and/or various other computingentities.

In another embodiment, the computing entity 110 may include one or morecomponents or functionality that are the same or similar to those of thelogistics server(s) 105, as described in greater detail above. As willbe recognized, these architectures and descriptions are provided forexemplary purposes only and are not limiting to the various embodiments.

FIG. 4A is a schematic diagram of an environment 400 illustrating howone or more assets are loaded into storage units inside a logisticsvehicle, according to some embodiments. The environment 400 includes aconveyor apparatus 425 that includes the reader component 410 and anoperator 405 that loads assets into one or more of the storage units423, which are located within the logistics vehicle 420. The environment400 also illustrates that the conveyor apparatus 425 is communicativelycoupled to the logistics vehicle 420 and/or the storage units 423 viathe network 435. In some embodiments, the logistics vehicle 420represents the logistics vehicle 120 and vice versa, the conveyorapparatus 425 represents the conveyor apparatus 125 and vice versa, thestorage units 423 represent the storage units 123 and vice versa, and/orthe network(s) 435 represents the network(s) 135.

A “logistics vehicle” as described herein is any suitable vehicle (e.g.,an airplane, freight ship, carrier van, drone, UMV or autonomous car,etc.) that performs or is associated with any suitable logistics orshipping operation. A “shipping operation” as described herein is anysuitable operation related to shipping, such as a final mile delivery ofassets (i.e., delivering assets to final destination location),delivering assets from one sorting facility to another, deliveringassets from a carrier store to a sorting facility, importing orexporting assets, flying or otherwise carrying assets to/away from asorting facility, etc. An “asset” as described herein is any tangibleitem that is transported from one location to another. Assets may be orinclude the contents that enclose products or other items people wish toship. For example, an asset may be or include a parcel or group ofparcels, a package or group of packages, a box, a crate, a drum, acontainer, a box strapped to a pallet, a bag of small items, and/or thelike.

Logistics vehicles may be configured to house or receive storage unitsfor the storage of assets. A “storage unit” as described herein is anytangible area or enclosure that is configured to store or receive one ormore assets. For example, a storage unit can be or include: one or moreshelf slots, one or more containers, a locker bank, a cage, one or morecubbies, one or more drawers, and/or any other partial or full enclosurethat receives assets.

In some embodiments, the logistics vehicle 420 and/or the storage units423 anticipate the asset traversing sequence as they move toward theoperator 405's position and shifts or rotates the storage units 423 inadvance such that by the time an asset is picked from the conveyorapparatus 425, the particular corresponding storage unit positions (oris already positioned) at the appropriate loading location 407. A“loading location” as described herein is any suitable location forloading one or more assets onto a respective storage unit. The loadinglocation may be at or close to an area where an operator or otherloading mechanisms (e.g., a robotic arm component) performs the loadingoperations. For example, the loading location may be at the rear of thelogistics vehicle 420 (as illustrated in FIG. 4A), on the side of thelogistics vehicle 420, and/or on the rear wall inside of a cab of thelogistics vehicle 420 such that a driver can load parcels just beforeengaging in driving, for example.

The environment 400 illustrates that the conveyor apparatus 425 and thelogistics vehicle 420 (and/or the storage units 423) are communicativelycoupled. In some embodiments, a “conveyor apparatus” as described hereinincludes any suitable conveyor belt assembly that includes a conveyorbelt (continuous medium that carries assets from one location toanother) one or more rollers or idlers that rotate the belt or rotatesuch that assets are moved, and/or one or more pulleys (e.g., located onthe ends of the conveyor apparatus 425) that transmit drive power intothe belt. A conveyor apparatus, however, need not require a “belt” butcan use rollers or other mechanisms to move assets. In some embodiments,“communicatively coupled” means that two or more components can performdata transportation between each other via a wired (e.g., ethernet orfiber-optic medium connected in a LAN) or wireless (e.g., IEEE 802.15.4)computer protocol network. The conveyor apparatus 425 includes arotating component 425-1 (e.g., a belt or set of rollers) that isconfigured to cause movement of one or more assets for loading the oneor more assets. Each time the rotating component 425-1 causes movementof an asset past the reader component 410, the reader component 410reads the tag of each asset (e.g., assets 449, 447, and 445), which isthen transmitted over the network 435.

By being communicatively coupled, the conveyor apparatus 425, thelogistics server(s) 105, the logistics vehicle 420, and/or the storageunits 423 can share the sequence of assets that are traversing down theconveyor apparatus 425 (via the rotating component 425-1) based on thereader component 410 reading data from one or more tags located on eachasset and sharing the information, via the network 435, with thelogistics vehicle 420, the logistics server 105, and/or the storageunits 423. For example, the sequence of assets can include the asset 449(already read by the reader component 410 first), the next in-line asset447 (read by the reader component 410 after it read the asset 449), andthe asset 445 currently being read by the reader component 410. Thus thesequence may be populated in a data structure, such as a queue,indicating the sequence of assets 449, 447, and 445. This may beindicative of the order that assets need to be loaded. In this way, thestorage units 423 can rotate a corresponding storage unit to the loadinglocation based on the next-in-line asset and/or identifiers located onthe tag (e.g., destination address or dimensions of the correspondingasset). In an illustrative example, in response to the first asset 449being read by the reader component 410 (e.g., because a belt (e.g., therotating component 425-1) of the conveyor apparatus 425 has moved theasset 449 under the reader component 410) the reader component 410 maycommunicate, via the network 435, with the storage units 423, whichcauses a control signal to be sent so that a first storage unit can berotated to the loading location 407. The operator 405 may then load theasset 449 into the first storage unit at the loading location 407.Likewise, at least partially in response to the reader component 410reading the second asset 447 (e.g., because the belt of the conveyorapparatus 425 has moved the asset 447 under the reader component 410),the reader component 410 may communicate, via the network 435, with thestorage units 323, which causes another control signal to be sent to asecond storage unit such that the second storage unit can take the placeof the first storage unit (i.e., move to the loading location 407). Theoperator 405 can then load the second asset 447 into the second storageunit at the loading location 407. This process can be repeated for thethird asset 445 (and all other assets traversing in a sequence down theconveyor apparatus 42), such that a third storage unit is rotated to theloading location 407, taking the place of the second storage unit sothat the operator 405 can load the third asset 445 into the thirdstorage unit at the loading location 407. In this way, as the conveyorapparatus 425 moves each asset downstream past the reader component 410,the reader component 410 (or other component) can transmit an identifieridentifying each asset such that the logistics server(s) 105, thelogistics vehicle 420, and/or the storage units 423 can store thesequence of assets being read so that the storage units 423 can rotatethe correct storage unit to the loading location based on the particularsequence order that the assets were read in and identifier data locatedin each tag coupled to each asset.

In some embodiments, the storage units 423 (or any of the storage unitsdescribed herein) rotate individual storage units to the location byshifting storage units (also called storage structures) within a storagespace in order to facilitate efficient staging and/or retrieval ofassets or parcels. Examples of this are described in U.S. applicationSer. No. 16/557,573 titled “Systems, methods, and apparatuses forshifting and staging storage structures and parcels thereon,” filed onAug. 30, 2019, the contents of which are incorporated by reference inits entirety.

FIG. 4A illustrates at least in part, the eased burden the operator 405faces relative to prior solutions in the shipping industry. For example,the operator 405 need not walk into the logistics vehicle 420. In priorsolutions, a logistics vehicle may include shelving units along thewalls of the logistics vehicle and an operator would have to physicallystep up into the logistics vehicle and find the correct loading locationfor a particular asset (e.g., based on manually matching information ona label of an asset with information located on the shelving unit).However, embodiments improve these loading systems because, instead ofmoving around the logistics vehicle 420, the operator 405 may stand atthe loading location 407 and place the asset in the particular storageunit at the particular loading location 407 since the storage units 423automatically rotate to the loading location 407 as described above. Inthis way, the particular storage unit moves to where the operator 405is, as opposed to the operator 405 having to move where the correctstorage unit is.

In some embodiments, the storage units 423 can be accessed from anysuitable loading location associated with the logistics vehicle 420. Forexample, in some embodiments, the storage units 423 can be accessed fromthe side, front (rear wall of the cab), or rear of the logistics vehicle420. In some embodiments, panels (not shown) can cover the loadinglocations during the storage unit shuffle cycle as part of an in-carmechanism.

In some embodiments, the storage units 423 may not rotate to the loadinglocation 407 fast enough (or they are rotating too fast) for theoperator 405. In these embodiments, the operator 405 can wait or doublehandle the asset (i.e., pick the asset from the conveyor apparatus 425,leave the asset in a buffer storage unit (described below), and push theasset from the buffer storage unit to the appropriate storage unit ofthe storage units 423 at a later time).

FIG. 4B is a more detailed view of the reader component 410 of FIG. 4A,according to particular embodiments. Although FIG. 4B illustrates thereader component 410 of FIG. 4A, FIG. 4B may be any reading componentdescribed herein with regard to several embodiments. FIG. 4B includesthe conveyor apparatus 425, the reader component 410, and the assets 445and 447. FIG. 4B illustrates the reader component 410 reading a tag 440of the asset 445 in response to the conveyor apparatus 525 causing theasset 445 to move past the reader 410-2. As illustrated, the readercomponent 410 is coupled to or a part of the conveyor apparatus 425,with the reader 410-2 specifically being oriented in a position higherthan the surface of the conveyor apparatus 425 so that the reader 410-2can read each tag of each asset. Although the reader component 410 isillustrated as being attached or a part of the conveyor apparatus 425,it is understood that the reader component 410 or any other componentthat reads tags does not have to be attached to a conveyor apparatus andcan be oriented in any suitable position (e.g., on a ceiling or bestandalone) and can take on any suitable form (e.g., a sphere ortriangle) or any other configuration besides what is illustrated in FIG.4B.

The reader 410-2 reads the tag 440 that is coupled to the asset 445 andtransmits, via the transmitter 410-3 and the network 435, theidentifier(s) or value(s) located in the tag 440 to the logistics server105, the logistics vehicle 420, and/or the storage units 423, whichcauses a control signal to be transmitted to the storage units 423 torotate a corresponding storage unit to the loading location 407 based onthe data in the tag 440. Put another way, for example, a control signalcan be sent to the storage units 423 causing the appropriate storageunit to be rotated to the loading location 407 based on the“destination,” “size” of the asset 445, and/or “type” of asset 445. Forexample, the storage units 423 may include irregular shaped or differentshaped storage units, some of which are each configured to store assetsof differing sizes or weights, for example. Accordingly, for instance,if the asset 445 was considered a “small” asset, the storage units 423may include a first storage unit configured to store smalls.Accordingly, in response to the reader 410-2 reading the tag 440, thefirst storage unit may be rotated to the loading location 407 to matchthe storage unit storage size capacity to the size of the asset.

Although the tag 440 includes specific identifiers and values, such asdestination (e.g., address where asset is delivered to), size (e.g.,weight or dimensions), and type (e.g., smalls, drum, box), it isunderstood that this is representative and that any identifier or valuesassociated with a corresponding asset can alternatively or additionallybe stored to any tag and be used to rotate a corresponding storage unitto the loading location based on the identifier data. For example, thetag 440 may alternatively or additionally include other attributes oridentifiers, such as: shipper name, fragileness of the asset, the levelof security associated with the asset (e.g., high security assets may bekept in a safe container of the plurality of storage units 423),indications of whether shipment is expedited, zip code, whether asset isdomestic or foreign, etc. Some or each of these identifiers can be usedto rotate an appropriate storage unit to the loading location 407 (orany other loading location described herein). For example, if the tag440 has an identifier indicating that the corresponding asset 445 is“fragile,” the storage units 423 may include a specialized storage unitthat include fasteners (e.g., hook and loop fasteners) that areconfigured to hold fragile assets in place so that they do not rattle orotherwise move so that there is no breakage of the contents of theasset. In this way, for example, in response to the reader 410-2 readingthe “fragile” identifier within the tag 440, a control signal may besent to the storage units 423, which causes the storage unit with thefasteners to be rotated to the loading location 407 so that the operator405 may not only load the “fragile” asset 445 into the correct storageunit, but the operator 405 may place the fasteners over the asset 445 sothat the asset 445 stays substantially stationary. It is understood thatsome or each of the identifiers in the tag 440 can be used to cause astorage unit to rotate to the loading location. For example, eachidentifier may take on a certain weight or importance such that a linearcombination score or calculation may be done to determine the final votefor a storage unit. In these instances, some identifiers (e.g., weightand size) may be more indicative of requiring a particular storage unit,whereas other identifiers (e.g., fragileness) may be more important andindicative of requiring a second storage unit. However, the otheridentifiers may be weighted higher or important for voting on aparticular storage unit to load the asset to. Accordingly, the secondstorage unit may win the vote or be chosen as the storage unit to berotated to the loading location, as opposed to the first storage unitbecause an asset is fragile (more important) notwithstanding that otherstorage units may be a better fit for the particular-sized asset.

In some embodiments, the transmitter 410-3 alternatively or additionallyrepresents a receiver or transceiver in order to receive feedback (e.g.,from the logistic server(s) 105, the storage units 423, and/or thelogistics vehicle 420) to cause modification of the conveyor apparatus425 in some way. For example, such modification may include an automaticcontrol signal to slow down or stop the conveyor apparatus 425 (e.g.,because an imaging camera sensor containing object recognitionalgorithms senses the operator 405 moving slowly). In another example,the conveyor apparatus 425 may include a speaker (not shown) thatprovides auditory feedback to the operator 405 (e.g., an instruction tospeed up, slow down, or notify the operator 405 of certain datalocated/not located in the tag 440).

In some embodiments the reader 410-2 and tag 440 (or any otherreader/tag combination described herein) are RFID, NFC, or any othersuitable combination of reader and/or tag devices equipped with antennasand the like. In some embodiments, each tag is passive, active, orsemi-passive. One embodiment of an RFID tag may include an active RFIDtag, which comprises at least one of the following: (1) an internalclock; (2) a memory; (3) a microprocessor; and (4) at least one inputinterface for connecting with sensors located in the reader component410. Another embodiment of the RFID tag may be a passive RFID tag. EachRFID tag may communicate wirelessly with RFID interrogators or readers(e.g., the reader 410-2 of FIG. 4B) within a certain geographical rangeor signal strength threshold of each other.

It is understood that in particular embodiments, a “tag” and a “reader”are not limited to RFID, NFC, or similar technologies but may broadlyinclude other embodiments where any data is read from any suitablemedium by a computer-readable machine. For example, a “tag” may be orinclude a paper or other medium that includes a barcode, QR code, datamatrix code, smart code, or other code or computer-readable indicia ofidentifiers. In these embodiments, any suitable associated machinereader can be used to read the code of identifiers, such as anelectronic scanner (e.g., a bar code scanner). Accordingly, the reader410-2 may represent an electronic scanner, QR code reader, NFC reader,or any variety of suitable readers.

FIG. 5 is a schematic diagram of an environment 500 illustrating how oneor more assets are loaded into storage units inside a logistics vehicle,according to some embodiments. The environment 500 includes a conveyorapparatus 525 that includes the reader component 510 and a roboticcomponent 505 (e.g., a robotic arm) that loads assets into one or moreof the storage units 523, which are located within the logistics vehicle520. The environment 500 also illustrates that the conveyor apparatus525 is communicatively coupled to the logistics vehicle 520 and/or thestorage units 523 via the network 535. In some embodiments, thelogistics vehicle 520 represents the logistics vehicle 120 and viceversa, the conveyor apparatus 525 represents the conveyor apparatus 125and vice versa, the storage units 523 represent the storage units 123and vice versa, and/or the network(s) 535 represents the network(s) 135.

In some embodiments, each component of the environment 500 representsthe corresponding component of the environment 400 of FIGS. A and/or 4Band all of the functionality described, except for the robotic component505. That is, in some embodiments, the conveyor apparatus 525 mayrepresent the conveyor apparatus 425, the reader component 510 mayrepresent the reader component 410, the network 535 represents thenetwork 435, the logistics vehicle 520 represents the logistics vehicle420, the storage units 523 represent the same storage units 423, and thelike. Accordingly, all functionality described above with respect toFIGS. 4A and 4B may be the same for FIG. 5, except for the roboticcomponent 505.

FIG. 5 illustrates that a robotic component 505 may be used to loadassets instead of a human operator (e.g., the operator 405 of FIG. 4A).The robotic component 505 may be any suitable special-purpose machineconfigured to move assets to the loading location 507 and intocorresponding storage units. In some embodiments, robotic component 505represents a robotic arm component that is configured to clasp assets(e.g., via pressure sensors) and move them to the loading location 507(e.g., via actuators). For example, the robotic component 505 can be arobotic arm, such as a Cartesian robot, cylindrical robot, SCARA robot,articulated robot, anthropomorphic robot, a VEX robotic arm, etc. Insome embodiments, the robotic component 505 can alternatively representany suitable robotic mechanism or machine that is not a robotic arm. Forexample, the robotic component 505 can represent an unmanned autonomousvehicle (UAV), drone, or other robotic machine that has a platform(e.g., instead of an arm or fingers) or enclosure to receive assets andcan use an actuator to push the assets to the appropriate storage unitat the loading location 507.

In some embodiments, the robotic component 505 (or any robotic componentdescribed herein) is equipped with one or more sensors (not shown) inorder to detect presence of the assets on the conveyor apparatus 525 (orany conveyor apparatus) and/or determine where exactly to place assetsat a loading location. For example, in some embodiments, a roboticcomponent includes a camera that uses object detection or objectrecognition algorithms to detect that an asset is within a distancethreshold. In response to this detection, it can clasp the nearest asset(or group of assets) within the distance threshold and place the assetin the storage unit at the loading location 507 using object detection(e.g., a bounding box that reads “storage unit” may be detected at theloading location 507). Alternatively or additionally, the roboticcomponent includes a reader (e.g., a QR, RFID, NFC) that is configuredto read a tag or other indicia on the asset such that in response to aread of the tag, the robotic component clasps or otherwise moves anasset to a loading location and into a storage unit. Alternatively oradditionally, the robotic component includes a range finder sensor suchthat in response to the asset being read to be within a range threshold,the robotic component may clasp or otherwise move an asset to a loadinglocation and into a storage unit. Alternatively or additionally, therobotic component includes a pressure sensor such that in response tothe robotic component reading or experiencing a pressure over athreshold, it clasps or otherwise moves an asset to a loading locationand into a storage unit.

In some embodiments, the robotic component 505 (or any other roboticcomponent described herein) is equipped with a transmitter, receiver, ortransceiver (not shown) in order to communicate with the othercomponents within the environments 500 and/or 100 via the network 535 tomodify its operations. For example, in response to the reader component510 reading an asset, it can establish a connection with the roboticcomponent 505 such that the robotic component 505 has informationindicating the sequence in which assets are read to prepare for loading(e.g., to widen or narrow its clasping mechanism based on the size of aparticular incoming asset) according to the sequence read. Alternativelyor additionally, the storage units 523 can send, via a transmitter, amessage to the robotic component 505 instructing the robotic component505 to stop or otherwise slow its operations (e.g., because the rotatingof the storage units 523 is taking too long or loading is occurring toofast). Alternatively or additionally, the logistics server(s) 105 or anyother suitable component may notify the robotic component 505 that oneor more assets were placed in a wrong storage unit or there hasotherwise been a change in status for an associated asset (e.g., achange in destination address). The logistics server(s) 105 or othercomponent may then cause the storage unit associated with the change instatus to be moved to the loading location 507 and the logisticsserver(s) 105 or other component instruct the robotic component 505 toremove the asset. Responsively, a control signal may be sent to thestorage units 523 to once again rotate an appropriate storage unit tothe loading location 507 based on the status change. Responsively, therobotic component 505 may place the asset that was removed from theother storage unit to the new storage unit based on the status change.

FIG. 5 Illustrates that similar to a manual loading process by anoperator, the robotic component 505 may be used to pick an asset andmove it to the storage unit presented at the loading location 507. Inembodiments, both the robotic component 505 and the storage units 523work in sync such that the storage units 523 are responsible forrotating the correct individual storage unit to the loading location 507based on the asset that the robotic component 505 is currently claspingor otherwise needs to load next. In embodiments, an asset sequence isread upstream by the reader component 510, which triggers both storageunit selection and robotic component 505 operation.

In an illustrative example of how the robotic component 505 works withinthe environment 500, the following is provided. The reader component 510may first read a tag of an asset that has various identifiers (e.g.,weight, dimensions, destination address). Responsively, the readercomponent 510 may communicate, via the network 535, with the logisticsserver(s) 105, the logistics vehicle 520, and/or the storage units 523,which then causes or sends a control signal to the storage units 523 torotate a corresponding storage unit to the loading location 507 based onthe identifiers within the tag. Responsively, the robotic component 505may load the asset into the storage unit at the loading location 507.This process can then be repeated for other tags and assets traversingdown the conveyor apparatus 525 based on the sequence or order each tagof each asset was read in and based on the identifiers in thecorresponding tag.

FIG. 6 is a schematic diagram of an environment 600 illustrating how oneor more assets are loaded into storage units that are outside of alogistics vehicle, according to some embodiments. The environment 600includes a conveyor apparatus 625 that includes the reader component610, a robotic component 605 (e.g., a robotic arm) that loads assetsinto one or more of the storage units 623, which are located on aplatform 640 outside of the logistics vehicle 620. In some embodiments,the conveyor apparatus 625 is communicatively coupled to the logisticsvehicle 620 and/or the storage units 623 via a computer network (e.g.,135). In some embodiments, the logistics vehicle 620 represents thelogistics vehicle 120 and vice versa, the conveyor apparatus 625represents the conveyor apparatus 625 and vice versa, and/or the storageunits 623 represent the storage units 623 and vice versa.

In some embodiments, one or more components of the environment 600represent the corresponding component of the environment 500 of FIG. 5and all of the functionality described, except for the platform 640.That is, in some embodiments, the conveyor apparatus 625 may representthe conveyor apparatus 525, the reader component 610 may represent thereader component 510, the logistics vehicle 620 represents the logisticsvehicle 520, the storage units 623 represent the same storage units 523,the robotic component 605 represents the robotic component 505, and thelike. A “platform” as described herein includes any apparatus that israised (e.g., 2 or 3 feet) from a ground surface (e.g., the groundsurface 650) and that includes a flat or substantially flat surfaceconfigured to receive storage units such that storage units may beplaced on the surface of the platform.

FIG. 6 illustrates that the storage units can include or be place onto abuilding-based rail system 623-1 (that abuts the platform 640) that isconfigured to rotate and shuffle an individual storage unit to a loadinglocation. In some embodiments, the building-based rail system is therail system described in U.S. application Ser. No. 16/557,573 titled“Systems, methods, and apparatuses for shifting and staging storagestructures and parcels thereon,” filed on Aug. 30, 2019, the contents ofwhich are incorporated by reference in its entirety. FIG. 6 furtherillustrates that the storage units 623 can rotate and shift outside ofthe logistics vehicle 620. This is because a logistics vehicle is notnecessarily needed for sorting. For example, each logistics vehicle maybe in use or otherwise occupied such that there are none available forloading. In these embodiments, the platform 640 can be used to place thestorage units 623 on. In this way, assets can be loaded onto the storageunits 623 and, when a logistics vehicle (e.g., logistics vehicle 620) isavailable, the storage units 623 (including the rail system 623-1) canbe loaded from the platform 640 into the logistics vehicle 620. Forexample, the rail system 623-1, with some or all of the correspondingassets stored thereon, can be pushed from the platform 640 through theback of the logistics vehicle 620 and onto its bed after each asset hasbeen loaded.

In an example illustration of how components may work together withinthe environment 600, the reader component 610 may first read a set ofasset tags that are attached to corresponding assets. The readercomponent 610 may communicate with the logistics server(s) 105 and/orthe storage units 623, thereby causing, for example, the rail system623-1 to shuffle one or more storage units of the storage units 623 to aloading location based on the identifiers in the asset tags indicativeof the asset attributes and sequence. Responsively, the roboticcomponent 605 may pick or place the corresponding asset into theshuffled or rotated storage unit. Subsequent to the loading of eachasset that traverses the conveyor apparatus 625, the entire storageunits 623 (e.g., including the rail system 623-1) may be pushed orotherwise moved from the platform 640 into the back of the logisticsvehicle 620.

FIG. 7 is a schematic diagram of an environment 700 illustrating how oneor more assets are loaded into storage units that are outside of alogistics vehicle, according to some embodiments. The environment 700includes a conveyor apparatus 725 that includes the reader component 710and a human operator 705 that loads assets into one or more of thestorage units 723, which are located on a ground surface 750 outside ofthe logistics vehicle 720. In some embodiments, the conveyor apparatus725 is communicatively coupled to the logistics vehicle 720 and/or thestorage units 723 via a computer network (e.g., 135). In someembodiments, the logistics vehicle 720 represents the logistics vehicle120 and vice versa, the conveyor apparatus 725 represents the conveyorapparatus 725 and vice versa, and/or the storage units 723 represent thestorage units 723 and vice versa.

In some embodiments, one or more components of the environment 700represent the corresponding component of the environment 600 of FIG. 5and all of the functionality described, except for the platform 640 andthe operator 705. That is, in some embodiments, the conveyor apparatus725 may represent the conveyor apparatus 625, the reader component 710may represent the reader component 610, the logistics vehicle 720represents the logistics vehicle 620, and/or the storage units 723represent the same storage units 623.

FIG. 7 illustrates that a human operator 705 can be used instead of arobotic component (e.g., robotic component 605) and that a platform(e.g., the platform 640) does not necessarily need to be used to loadassets. Rather, the storage units 723 can be placed directly on theground surface 750. FIG. 7 also illustrates that the storage units 723can be loaded into or include a building-based rail system 723-1. Insome embodiments, the rail system 723-1 represents the samebuilding-based rail system 623-1 of FIG. 6.

In an illustrative example of how assets may be loaded in theenvironment 700, the reader component 710 may first read a sequence oftags corresponding to a plurality of assets. The identifiers in each tagcan be transmitted, via a computer network and from the reader component710 to a logistics server(s) 105. The logistics server(s) 105 may thensend a control signal, via the computer network, to the building-basedrail system 723-1 to rotate or shift the storage units 723 to a loadinglocation based on the information on each tag, according to the sequenceof tags or assets. For instance, a first asset that is read first may bevery large and so a first storage unit configured to store large assetsis first shifted to a loading location. Responsively, a second-in-lineasset that is read second after the first asset may have identifiersindicating that it is very small. Accordingly, the first storage unitmay be shifted away from the loading location while a second storageunit may be shifted to the loading location so that the second asset canbe loaded into the second storage unit. The second storage unit may beconfigured to receive small assets. In this way, individual storageunits can be shifted or otherwise rotated to a loading location based oncorresponding tag identifier data and sequence that a tag is read in fora particular asset.

FIG. 8A is a schematic diagram of an environment 800 illustrating howone or more assets are loaded into storage units that are configured tobe adjusted into a U-shape, according to some embodiments. Theenvironment 800 includes a conveyor apparatus 825, a human operator 805that loads assets into one or more of the storage units 823, which arelocated on a ground surface 850 outside of the logistics vehicle 820. Insome embodiments, the conveyor apparatus 825 is communicatively coupledto the logistics vehicle 820 and/or the storage units 823 via a computernetwork (e.g., 135). In some embodiments, the logistics vehicle 820represents the logistics vehicle 120 and vice versa, the conveyorapparatus 825 represents the conveyor apparatus 125 and vice versa,and/or the storage units 823 represent the storage units 123 and viceversa.

In some embodiments, one or more components of the environment 800represent the corresponding component of the environment 700 of FIG. 7and all of the functionality described, except for the storage units723. That is, in some embodiments, the conveyor apparatus 825 mayrepresent the conveyor apparatus 725, and the logistics vehicle 820represents the logistics vehicle 720.

FIG. 8A illustrates that the storage units 823 are adjustable in orderto make them accessible for loading. For example, as illustrated in FIG.8A, the storage units 823 can be oriented in a U-shape, which ensureseach storage unit is accessible by the operator 805. In someembodiments, the operator 805 can use a load chart that specifies whichpostcode goes with which chart so that the operator 805 can load anincoming asset to a correct storage unit. Although, the storage units823 are illustrated as being oriented in a U shape, it is understoodthat this is illustrative only and that the storage units 823 can beadjusted and/or oriented in any suitable shape that allows access, suchas orienting the storage units 823 in a circular shape, a single line, apartial oval, and the like. Various embodiments contain components(described with respect to FIG. 8B) that allow such orientation in anysuitable shape or fashion.

FIG. 8B is an upper front view of storage units illustrating howindividual storage units 823-1 and 823-2 may be oriented and adjusted inorder to contribute to the overall U-shape (or any other suitable shape)of the storage units 823, according to some embodiments. As illustratedin FIG. 8B, the storage unit 823-1 includes a top-inner surface 823-1D,a top-upper surface 823-1E, an inside edge 823-1A that extends from thetop-inner surface 823-1D down to the bottom surface 823-1G, an outsideedge 823-1B that extends from the top outer surface 823-1F to the bottomsurface 823-1G, and an adjustable shelf 823-1C. Likewise, the storageunit 823-2 includes a top-inner surface 823-2D, a top-upper surface823-2E, an inside edge 823-2A that extends from the top-inner surface823-2D down to the bottom surface 823-2G, an outside edge 823-2B thatextends from the top outer surface 823-2F to the bottom surface 823-2Gand an adjustable shelf 823-2C.

As illustrated, the inside edges 823-1A and 823-2A (or at least theupper portion of these edges) are fixed, attached, or otherwise coupledtogether via the fastening mechanism 870. The fastening mechanism 870may be any suitable fastening mechanism, such as a screw, hook and loopfastener, pin fastener, or the like that fastens at least a portion ofthe inside edges 823-1A and 823-2A. The fastening mechanism 870 causes afixed axis to be formed between the storage units 823-1 and 823-2 suchthat each storage unit 823-1 and 823-2 can swing or pivot about the axisin a 360 degree manner as illustrated by the arrows. For example, asillustrated in FIG. 8B, the top-inner surfaces 823-1D and 823-2D mayremain in a relatively fixed position due to the fastening mechanism870, whereas the top-upper surfaces 823-1E and 823-2E (which have theirown inner edges (illustrated in FIG. 8D)) can swing about the axis oraway from each other. This allows the U-shape to formulate asillustrated in FIG. 8A. In some embodiments, however, there need not bea fastening mechanism 870. Rather, the individual storage units 823-1and 823-2 can be individually placed in any suitable orientation orposition such that an entire units of storage units can take on anyshape, such as a U-shape as described herein (e.g., FIG. 8A).

The shelves 823-1C and 823-2C are adjustable in height parallel to oralong the inside and outside edges 823-1A, 823-2A, 823-1B, 823-2B. Thismay allow for an asset of almost any size to be accommodated by astorage unit. For instance, the shelf 823-1C can be moved higher (e.g.,near the inner-upper edge 823-1D) to allow the large asset 840 to bestored in a larger area and the smaller assets 842 to be stored in asmaller area relative to the larger area. The adjusting may occur viaany suitable mechanism. For example, the edges 823-1A, 823-2A, 823-1B,823-2B may include peg holes that are configured to receive pegs thatare attached to the shelves 823-1C and/or 823-2C. In this way, each peghole corresponds to a particular height adjustment. In another example,the shelves 823-1C and/or 823-2C may be moved by hydraulic mechanisms,roller mechanisms, or any other suitable mechanism.

FIG. 8C is a top view of the storage units 823-1 and 823-2 of FIG. 8Billustrating how individual storage units 823-1 and 823-2 may beoriented and adjusted in order to contribute to the overall U-shape (orany other suitable shape) of the storage units 823. The fasteningmechanism 870 causes a fixed axis to be formed between the storage units823-1 and 823-2 such that each storage unit 823-1 and 823-2 can pivotabout the axis in a 360 degree manner as illustrated by the arrows inFIG. 8C. The top-inner surfaces 823-1D and 823-2D may remain in arelatively fixed position due to the fastening mechanism 870, whereasthe top-upper surfaces 823-1E and 823-2E (which have their own inneredges (not shown)) can swing about the axis or away from each otherbecause they do not have their own fastening mechanism connecting edges.This allows the U-shape to formulate as illustrated in FIG. 8A.Alternatively, the top-upper surfaces 823-1E and 823-2E can swing aboutthe axis or towards each other. This movement would cause the storageunits 823-1 and 823-2 to be aligned such that not only are the inner-topsurfaces 823-1D and 823-2D connected or aligned, but also the upper topsurfaces 823-1E and 823-2E can be connected or aligned. By beingaligned, these storage units (and any other plurality of storage units)together can form a straight line of storage units, as opposed to aU-shaped or other non-line non-row shape as illustrated in FIG. 8A.

FIG. 8D is a rear view of the storage units 823-1 and 823-2 of FIG. 8Billustrating how individual storage units 823-1 and 823-2 may beoriented and adjusted in order to contribute to the overall U-shape (orany other suitable shape) of the storage units 823, according to someembodiments. The fastening mechanism 870 causes a fixed axis to beformed between the storage units 823-1 and 823-2 such that each storageunit 823-1 and 823-2 can move about the axis in a 360 degree manner asillustrated in FIG. 8D. The top-inner surfaces 823-1D and 823-2D mayremain in a relatively fixed position due to the fastening mechanism870, whereas the top-upper surfaces 823-1E and 823-2E and correspondingedges 860 and 861 can swing about the axis or away from each otherbecause they do not have their own fastening mechanism connecting edges.This allows the U-shape to formulate as illustrated in FIG. 8A.Alternatively, the top-upper surfaces 823-1E and 823-2E and edges 860and 861 can swing about the axis or towards each other. This movementwould cause the storage units 823-1 and 823-2 to be aligned such thatnot only are the inner-top surfaces 823-1D and 823-2D connected oraligned, but also the upper top surfaces 823-1E and 823-2E and edges 860and 861 can be connected or aligned. By being aligned, these storageunits (and any other plurality of storage units) together can form astraight line of storage units, as opposed to a U-shaped or othernon-line non-row shape.

Referring back to FIG. 8A, after assets are loaded into correspondingstorage units, in some embodiments the entire system of storage units823 can be loaded into the logistics vehicle 820. This can happen in anysuitable manner, such as by folding storage units each connected via afastening mechanism (e.g., identical to the fastening mechanism 870)such that each storage unit is stacked against a corresponding storageunit via moving about an axis formed by a fastening mechanism. Forexample, this is illustrated by the stacked storage units 723 of FIG. 7.

FIG. 9 is a schematic diagram of an environment 900 illustrating how oneor more assets are loaded into storage units that are configured to beadjusted into a semi-circle shape, according to some embodiments. Theenvironment 900 includes a conveyor apparatus 925, a robotic component905 that loads assets into one or more of the storage units 923, whichare located on a platform 940 outside of the logistics vehicle 920. Insome embodiments, the conveyor apparatus 925 is communicatively coupledto the logistics vehicle 920 and/or the storage units 923 via a computernetwork (e.g., 135). In some embodiments, the logistics vehicle 920represents the logistics vehicle 120 and vice versa, the conveyorapparatus 925 represents the conveyor apparatus 125 and vice versa,and/or the storage units 923 represent the storage units 123 and viceversa.

In some embodiments, one or more components of the environment 900represents the corresponding component of the environment 800 of FIG. 8Aand all of the functionality described, except for the storage units 923and the platform 940 and the robotic component 905. In some embodiments,the storage units 923 represent the same storage units 823 of FIG. 3except there are fewer storage units. In this way, each storage unit canbe manually fastened or connected or disconnected (e.g., via thefastening mechanism 870) so that more or less storage units can be addedor removed from an entire storage unit assembly (i.e., a plurality ofstorage units).

FIG. 9 illustrates that the storage units 923 are adjustable in order tomake them accessible for loading and that a robotic component 905 can beused (instead of a human operator) and that a platform 940 placed on aground surface 950 can be used (instead of a ground surface only).Specifically, the storage units 923 can be adjusted in shapes other thana complete U-shape, as illustrated in FIG. 8A. For example, FIG. 9illustrates that the storage units 923 can be shaped in a semi-circularmanner for accessibility by the robotic component 905 for loading.Fastening mechanisms, as described with respect to the fasteningmechanism 870 of FIG. 8B can make this orientation possible. In anillustrative example, each inside edge of the storage units 923-1,923-2, 923-3, 923-4, and 923-5 may all be connected via a fasteningmechanism identical to fastening mechanism 870. For example, the storageunits 923-1 and 923-2 may each represent or include the same componentsor functionality described with respect to the storage units 823-1 and823-2 of FIGS. 8B and 8C. Accordingly, this may allow each storage unitto be oriented in a particular fashion about an axis associated with thefastening mechanism given that there is no corresponding fasteningmechanism on a rear portion of the storage units 923.

FIG. 10 is a schematic diagram of an environment 1000 illustrating howone or more buffer shelves are used for loading one or more assets,according to some embodiments. The computing environment 100 includes aconveyor apparatus 1025 that includes the reader component 1010, anoperator 1005 that loads assets into one or more of the storage units523, which are located within the logistics vehicle 520. The operator1005 can additionally or alternatively load one or more assets into thebuffer shelves 1033 and 1030. In some embodiments, the conveyorapparatus 1025 is communicatively coupled to the logistics vehicle 1020and/or the storage units 1023 via the network 135. In this manner, insome embodiments, the logistics vehicle 1020 represents the logisticsvehicle 1020 and vice versa, the conveyor apparatus 1025 represents theconveyor apparatus 125 and vice versa, and/or the storage units 1023represent the storage units 123 and vice versa.

In some embodiments, each component of the environment 1000 representsthe corresponding component of the environment 400 of FIGS. 4A and/or 4Band all of the functionality described, except for the buffer shelves1033 and 1030. That is, in some embodiments, the conveyor apparatus 1025may represent the conveyor apparatus 425, the reader component 1010 mayrepresent the reader component 410, the logistics vehicle 1020represents the logistics vehicle 420, the storage units 1023 representthe same storage units 423, and the like. Accordingly, all functionalitydescribed above with respect to FIGS. 4A and 4B may be the same for FIG.5, except for the buffer shelves 1030 and 1033.

FIG. 5 illustrates that the buffer shelves 1033 and 1030 mayadditionally be used to load assets to. A “buffer shelf” as describedherein is a particular storage unit that is configured to receive orstore one or more assets based on the one or more assets sharing a samedestination location as part of a final mile delivery (e.g., delivery ofasset to a particular home or business address) or other shippingoperation delivery. In these embodiments, a particular shipment ordelivery may have a plurality of assets that are to be delivered to thesame destination location. For example, a shipper may order a system orapparatus that has several component pieces that are all shipped asdifferent assets. In some instances, a first storage unit of the storageunits 1023 may be full or otherwise occupied for a particulardestination location. In these instances, the buffer shelf 1030 and/or1033 may be used to load other assets that are to be shipped to the samedestination location as the asset(s) loaded to the first storage unit.Subsequent to all assets being loaded, the buffer shelves 1030 and 1033can be loaded into the logistics vehicle 1020.

In an illustrative example, a first asset or tag may traverse past thereader component 1010, which receives information that the first assetis to be delivered to a first destination address. At least partiallyresponsive to this first information that the first asset is to bedelivered to the first destination address, the reader component 1010may communicate, via a computer network, with the logistics server(s)105, the logistics vehicle, 1020 and/or other component to send acontrol signal to the storage units 1023, causing a first storage unitconfigured to receive assets associated with the first asset (e.g.,within the same zip code, street, geofence, etc.) to rotate or shift toa loading location that the operator 1005 is standing at. Accordingly,the operator 1005 may load the first asset into the first storage unit.Subsequent to this, the reader component 1010 may read another asset (asecond asset) or corresponding tag indicating that the second asset isto be shipped to the same first destination address as the first asset.At least partially responsive (and/or responsive to embodimentsindicating that there is no room left in the corresponding first storageunit) the reader component 1010 transmitting this indication that thesame first destination address, the logistics server(s) 105, the storageunits 1023, and/or the logistics vehicle 1020 may cause a notificationto be transmitted to a computing entity 110 associated with the operator1005 instructing the operator 1005 to place the second asset into thebuffer shelf 1030 and/or 1033. Such notification can occur via anysuitable mechanism and does not necessarily require a computing entity110. For example, the reader component 1010, the logistics vehicle 1020,the storage units 1023, and/or the buffer shelves 1030/1033 may includean auditory speaker that is configured to cause an auditory notificationto be transmitted such that the operator 1005 can listen to the auditorynotification indicating to use the buffer shelf 1030 and/or 1033.Alternatively or additionally, other indicators may be provided, such asflashing lights or other indicators indicative of placing a particularasset on a buffer shelf.

FIG. 11 is a block diagram of an example queue data structure 1100illustrating how storage units can be rotated or shifted to a loadinglocation, according to some embodiments. The queue data structurerepresents a first-in-first out (FIFO) data structure where elements areprocessed in the order received by the data structure 1100. Each of theelements (labeled by their index 0, 1, 2, 3, and 4) represents aparticular tag or asset and all of its associated identifier data. In anillustrative example, element 0 indicating an asset ID of 1643 and thatit will be shipped to address A may represent some or all of theidentifiers in the tag 440 of FIG. 4B. In this way, each storage unitcan be rotated or shifted to a loading location based on the sequence ofelements in the data structure 1100 and its corresponding identifierdata. Although the identifiers only indicate two sets of data in thedata structure 1100—an asset ID and address data—it is understood thatthis is representative only and that any suitable identifiers can exist,such as those described with respect to the tag data of the tag 440 ofFIG. 4B, for example (e.g., size of asset, type of asset). Moreover,although the data structure 1100 represents a queue data structure, itis understood that this is representative only and that any suitabledata structure can be used, such as a hash map, last-in-first-out (LIFO)data structure, array, linked list, etc.

In an illustrative example of how the data structure 1100 is used torotate storage units, components associated with FIGS. 4B and 4A aredescribed. The reader 410-2 may first read a first tag of the asset 447at a first time. Responsively, the data in the tag can be populated atindex 0 of the data structure 1100. The data structure 1100 may bepopulated by the reader 410, the logistics server(s) 105, the logisticsvehicle 120, and/or storage units 123. Because index 0 represents the“front” of the data structure 1100 it is also immediately processed. Forexample, a first storage unit may be configured to store asset ID 1643based on its size, destination, and/or any other suitable information.Accordingly, the reader component 410 may transmit the data within thefirst tag, over a computer network, to a logistics server(s) 105 (orother component) which populates the data structure at element 0 andsends a control signal to the storage units 423 to rotate (at a secondtime subsequent to the first time) the first storage unit to the loadinglocation 407 based on information in the first tag.

Subsequent to the first time and/or the second time, the reader 410-2may read a second tag (e.g., corresponding to data of the tag 440) ofthe asset 445 at a third time. Responsively, the data in the second tagcan be populated at index 1 of the data structure 1100. Because index 1represents a position that is processed after index 0, element 1 isprocessed after element 0. For example, a second storage unit may beconfigured to store asset ID 1529 based on its size, destination, and/orany other suitable information. Accordingly, the reader component 410may transmit the data within the second tag, over a computer network, toa logistics server(s) 105 (or other component) which populates the datastructure at element 1 and sends a control signal to the storage units423 to rotate (at a fourth time subsequent to the third time) a secondstorage unit to the loading location 407 based on information in thesecond tag.

Subsequent to the third time and/or fourth time, the reader 410-2 mayread a third tag of a third asset at a fifth time. Responsively, thedata in the third tag can be populated at index 2 of the data structure1100. Because index 2 represents a position that is processed afterindex 1, element 2 is processed after element 1. For example, a thirdstorage unit may be configured to store asset ID 1326 based on its size,destination, and/or any other suitable information. Accordingly, thereader component 410 may transmit the data within the third tag, over acomputer network, to a logistics server(s) 105 (or other component)which populates the data structure at element 2 and sends a controlsignal to the storage units 423 to rotate (at a sixth time subsequent tothe fifth time) a third storage unit to the loading location 407 basedon information in the third tag.

Subsequent to the fifth and/or sixth time, the reader 410-2 may read afourth tag of a fourth asset at a seventh time. Responsively, the datain the fourth tag can be populated at index 3 of the data structure1100. Because index 3 represents a position that is processed afterindex 2, element 3 is processed after element 2. For example, a fourthstorage unit may be configured to store asset ID 1354 based on its size,destination, and/or any other suitable information. Accordingly, thereader component 410 may transmit the data within the fourth tag, over acomputer network, to a logistics server(s) 105 (or other component)which populates the data structure 1100 at element 3 and sends a controlsignal to the storage units 423 to rotate (at an eighth time subsequentto the seventh time) a fourth storage unit to the loading location 407based on information in the fourth tag.

Subsequent to the seventh and/or eighth time, the reader 410-2 may reada fifth tag of a fifth asset at a ninth time. Responsively, the data inthe fifth tag can be populated at index 4 of the data structure 1100.Because index 4 represents a last or “rear” position that is processedafter index 3, element 4 is processed after element 3 and is processedlast (e.g., indicating that there are no other assets on the conveyorapparatus 425). For example, a fifth storage unit may be configured tostore asset ID 1222 based on its size, destination, and/or any othersuitable information. Accordingly, the reader component 410 may transmitthe data within the fifth tag, over a computer network, to a logisticsserver(s) 105 (or other component) which populates the data structure1100 at element 4 and sends a control signal to the storage units 423 torotate (at a tenth time subsequent to the ninth time) the fifth storageunit to the loading location 407 based on information in the fifth tag.

Accordingly, FIG. 11 describes how a sequence of assets can beanticipated such that corresponding storage units can be rotated orshifted based on the particular sequence of elements corresponding toassets that are read and the actual identifier data in each asset. Thus,storage units can be rotated or shifted in a particular order based bothon the order in which assets or asset tags are read and the informationor identifiers contained in each individual tag.

IV. Exemplary System Operation

FIG. 12 is a flow diagram of an example process 1200 for causing astorage unit to rotate to a loading location to store one or moreassets, according to some embodiments. The process 1200 (and/or any ofthe functionality described herein) may be performed by processing logicthat comprises hardware (e.g., circuitry, dedicated logic, programmablelogic, microcode, etc.), software (e.g., instructions run on a processorto perform hardware simulation), firmware, or a combination thereof.Although particular blocks described in this disclosure are referencedin a particular order at a particular quantity, it is understood thatany block may occur substantially parallel with or before or after anyother block. Further, more (or fewer) blocks may exist than illustrated.Such added blocks may include blocks that embody any functionalitydescribed herein. The computer-implemented method, the system (thatincludes at least one computing device having at least one processor andat least one computer readable storage medium), and/or the computerprogram product/apparatus as described herein may perform or be causedto perform the process 1200, and/or any other functionality describedherein.

Per block 1201 one or more identifiers of one or more assets areobtained (e.g., by the logistics server(s) 105) in response to a readercomponent reading one or more tags associated with the one or moreassets. In some embodiments a conveyor apparatus that is configured torelay the one or more assets is used such that a first asset of the oneor more assets is configured to be picked from the conveyor apparatusand loaded onto a least one storage unit of a plurality of storage unitsfor one or more shipment operations. In particular embodiments, theconveyor apparatus is communicatively coupled to the plurality ofstorage units or communicatively coupled to one or more computingdevices (e.g., the logistics server(s) 105, the logistics vehicle 120,etc.) associated with the plurality of storage units. For example, thereader component may be attached or otherwise coupled to the conveyorapparatus such that each time each tag coupled to an asset traversespast the reader component (e.g., via a belt of the conveyor apparatus),one or more identifiers can be obtained by the reader component andtransmitted, over a computer network (e.g., the computer network 135),to the logistics server(s) 105, the computing entity 110, the logisticsvehicle 120, and/or the storage units 123. For example, referring backto FIG. 4A, the conveyor apparatus 425 may have a rotating component425-1 that is configured to cause movement of one or more assets forloading the one or more assets. Each time the rotating component 425-1causes movement of an asset past the reader component 410, the readercomponent 410 reads the tag of each asset (e.g., assets 449, 447, and445), which is then transmitted over the network 435.

An illustrative example of block 1201 is described herein with referenceto FIG. 4B. Referring back to FIG. 4B, the reader 410-2 may capture,interrogate, or otherwise read each tag on each asset 447 and 445 toreceive identifier(s), such as destination, size, and type of asset asindicated in the tag data of the tag 440. This information may then betransmitted, via the transmitting component 410-3, to the logisticsserver(s) 105, the computing entity 110, the logistics vehicle 120,and/or the storage units 123 so that one or more of these componentsobtain these identifiers per block 1201.

Per block 1203, a data structure indicative of asset sequence can bepopulated (e.g., at least partially in response to the obtaining of theone or more identifiers). In some embodiments, a queue data structure ispopulated with the obtained identifier(s) and other identifiersassociated with other assets that is indicative of an order that assetsare traversing on the conveyor apparatus or more specifically, the orderin which tags of assets are read. For example, referring back to FIG.11, the queue data structure 1100 in particular embodiments captures theorder that assets are traversing on a conveyor apparatus or the order inwhich tags of assets are read—a reader first reads a tag associated withasset ID 1643, which is then populated at index 0, the reader then readsa tag associated with asset ID 1529, which is then populated at index 1,the reader then reads a tag associated with asset ID 1326, which is thenpopulated at index 2, the reader then reads a tag associated with assetID 1354, which is then populated at index 3, the reader then reads a tagassociated with asset ID 1222, which is then populated at index 4. Inthis way, the data structure captures both the sequence in which assetsare read in (or traversing down a conveyor apparatus) and identifierdata associated with each asset (e.g., the size, weight, destinationaddress, etc.). Based both on the sequence order position of aparticular asset and the identifier data of each asset, a correspondingstorage unit can be rotated to a loading location, as described belowwith respect to block 1205.

Per block 1205, a storage unit of a plurality of storage units arecaused to automatically rotate to a loading location to receive or storethe one or more assets. In some embodiments, this is based on thenext-in-line index or element in the data structure and/or identifiersrendered by the tag as described above with respect to block 1203. Forexample, in some embodiments, the causing of the storage unit of theplurality of storage units to automatically rotate includes sending acontrol signal to the storage unit that rotates the storage unit to theloading location based at least in part on the identifier and the orderthe identifier is populated in the queue data structure, as described,for example, with respect to FIG. 11. In another illustrative example,referring back to FIG. 4B, at a first time the reader 410-2 may read thetag of the asset 447 as it traverses down the rotating component 425-1of the conveyor apparatus 425. The data or identifiers in this tag maythen responsively be transmitted, over the network 135, to a logisticsserver(s) 105, which populates a queue data structure indicating thatthis is the first element to be processed. Then at a second timesubsequent to the first time, the reader 410-2 may read the tag of asset445 as it is the next-in-line to traverse down the conveyor apparatus425. The data or identifiers in this tag—i.e., data of the tag 440—maythe responsively be transmitted, over the network 135, to the logisticsserver(s) 105, which populates the same queue data structure, indicatingthat this is the second element to be processed. Based on reading thefirst element in the queue data structure (corresponding to asset 447),the logistics server(s) 105 may send a control signal to the storageunit to rotate, shift, and/or otherwise move the first storage unit to aloading location. Based on reading the next-in-line element in the queuedata structure (corresponding to asset 445), the logistics server(s) maysend another control signal to another storage unit to rotate, shift, orotherwise move the second storage unit to the same loading location. Inthis way, the first storage unit is replaced with the second storageunit at the loading location based on the asset sequence reading orderand the identifier data in each tag. For instance, based on thepopulating of the data structure, embodiments cause, in near-real timerelative to the plurality of assets traversing on the conveyorapparatus, some or each storage unit of the plurality of storage unitsto rotate to the loading location in an order that the identifier andidentifiers are populated in the data structure.

In some embodiments, the precise timing of rotation of storage units tothe loading location occurs based on one or more sensor readings. Insome embodiments, pressure sensors located one each storage unit areused to determine timing of rotation. For example, referring to theillustrative example above, in response to the asset 447 being loaded(e.g., by an operator or robotic component) into the first storage unit,a first pressure sensor located on the first storage unit may read thatthe pressure is above a threshold (indicative of an asset having beenloaded thereon). Responsive to this reading, storage units 423 may readthe next element in a data structure (e.g., the queue data structure1100) indicating that the next asset to be loaded is asset 445 andresponsively cause rotation of the second storage unit to be rotated tothe loading location. Alternatively or additionally, a camera withobject recognition or detection algorithms can be used. For example,referring to the illustrative example above, in response to the asset447 being loaded (e.g., by an operator or robotic component) into thefirst storage location, a camera (e.g., located on the first storagelocation) may detect an asset is within a distance threshold (e.g., viaa range finder sensor). Responsive to this reading, storage units 423may read the next element in a data structure (e.g., the queue datastructure 1100) indicating that the next asset to be loaded is asset 445and responsively cause rotation of the second storage unit to be rotatedto the loading location. Alternatively or additionally, other sensorscan be used, such as counters or timers. Accordingly, after a certaintime threshold is met (e.g., 10 seconds, 20 seconds, etc.), storageunits can rotate to the loading location (e.g., based on next-in-lineelements in a data structure and asset identifiers).

In some embodiments, at least one storage unit of the plurality ofstorage units are configured to rotate to a loading location at leastpartially responsive to receiving a communication from the conveyorapparatus or the one or more computing devices indicating one or moreidentifiers associated with the first asset, as described, for example,with respect to FIGS. 4A and 4B. In some embodiments, this communicationcan occur because a conveyor apparatus may include a transmittingcomponent (e.g., transmitting component 410-3) that is configured totransmit, over a computer network, the identifier obtained by the readercomponent to the one or more storage units or one or more computingdevices associated with the one or more storage units such that the oneor more storage units are configured to rotate to a loading location forthe loading of the one or more assets in response to receiving theidentifier. In some embodiments, the transmitting, over the computernetwork, of the identifier occurs via a wireless communication linkbetween the conveyor apparatus, a computing device (e.g., the logisticsserver(s) 105 or computing entity 110), and a logistics vehicle that isconfigured to house the one or more storage units, as described, forexample, with respect to FIGS. 4A and 4B. Alternatively, in someembodiments, the transmitting, over the computer network of theidentifier occurs via a wired connection link between the conveyorapparatus and the one or more storage units, as described, for example,with respect to FIGS. 4A and 4B.

In some embodiments, the plurality of storage units are configured toreceive one or more assets associated with performing one or moreshipment operations and the plurality of storage units are located in alogistics vehicle and the logistics vehicle is configured to carry aplurality of assets associated with the one or more shipment operations(e.g., the logistics vehicle is configured to store assets to drop offat final-mile delivery destination addresses). This is described, forexample, with respect to FIG. 4A and FIG. 5. Alternatively, in someembodiments, the plurality of storage units are located on a platformadjacent to a logistics vehicle and the conveyor apparatus, asdescribed, for example, with respect to FIG. 9 and FIG. 6.

In some embodiments, the plurality of storage units are configured to beloaded into a logistics vehicle in response to the loading of the firstasset (or any asset) into the at least one storage unit, as described,for example, with respect to FIG. 9, FIG. 8A, FIG. 6, and FIG. 7. Forexample, referring back to FIG. 7, the storage units 723 (including therail system 723-1) may be loaded into the logistics vehicle 720 aftereach asset traversing down the conveyor apparatus 725 has been loadedinto the storage units 723.

In some embodiments, a robotic arm component is configured to performthe loading of the first asset (or any asset) into the at least onestorage unit of the plurality of storage units, as described, forexample, with respect to FIG. 9, FIG. 5, and FIG. 6. Alternatively, insome embodiments, a user operator performs the loading of the firstasset (or any asset) into the at least one storage unit of the pluralityof storage units. In some embodiments, one or more buffer shelves thatare configured to receive a set of assets based on the set of assetssharing a same destination location as part of a final mile delivery areused, as described, for example, with respect to FIG. 10.

In some embodiments the plurality of storage units are configured toreceive one or more assets associated with performing one or moreshipment operations. In some embodiments, the plurality of storage unitsare further configured to be placed inside and outside of a logisticsvehicle for loading or picking of the one or more parcels. For example,FIG. 4A through FIG. 10 describe that storage units can be locatedeither in a logistics vehicle or outside of the logistics vehicle, suchas on a ground surface or platform. In some embodiments, the pluralityof storage units include one or more fastening component (e.g., thefastening mechanism 870) that are configured to allow the plurality ofstorage units to be coupled together and the one or more fasteningcomponents further allow at least a portion of the plurality of storageunits to pivot about an axis. This is described, for example, withrespect to FIG. 8B, where the fastening mechanism 870 allows storageunits 823-1 and 823-2 to pivot about an axis so that a U-shape or othershape can be formed using a plurality of storage units.

Definitions

“And/or” is the inclusive disjunction, also known as the logicaldisjunction and commonly known as the “inclusive or.” For example, thephrase “A, B, and/or C,” means that at least one of A or B or C is true;and “A, B, and/or C” is only false if each of A and B and C is false.

A “set of” items means there exists one or more items; there must existat least one item, but there can also be two, three, or more items. A“subset of” items means there exists one or more items within a groupingof items that contain a common characteristic.

A “plurality of” items means there exists more than one item; there mustexist at least two items, but there can also be three, four, or moreitems.

“Includes” and any variants (e.g., including, include, etc.) means,unless explicitly noted otherwise, “includes, but is not necessarilylimited to.”

A “user” or a “subscriber” includes, but is not necessarily limited to:(i) a single individual human; (ii) an artificial intelligence entitywith sufficient intelligence to act in the place of a single individualhuman or more than one human; (iii) a business entity for which actionsare being taken by a single individual human or more than one human;and/or (iv) a combination of any one or more related “users” or“subscribers” acting as a single “user” or “subscriber.”

The terms “receive,” “provide,” “send,” “input,” “output,” and “report”should not be taken to indicate or imply, unless otherwise explicitlyspecified: (i) any particular degree of directness with respect to therelationship between an object and a subject; and/or (ii) a presence orabsence of a set of intermediate components, intermediate actions,and/or things interposed between an object and a subject.

A “data store” as described herein is any type of repository for storingand/or managing data, whether the data is structured, unstructured, orsemi-structured. For example, a data store can be or include one ormore: databases, files (e.g., of unstructured data), corpuses, digitaldocuments, etc.

A “module” is any set of hardware, firmware, and/or software thatoperatively works to do a function, without regard to whether the moduleis: (i) in a single local proximity; (ii) distributed over a wide area;(iii) in a single proximity within a larger piece of software code; (iv)located within a single piece of software code; (v) located in a singlestorage device, memory, or medium; (vi) mechanically connected; (vii)electrically connected; and/or (viii) connected in data communication. A“sub-module” is a “module” within a “module.”

The terms first (e.g., first request), second (e.g., second request),etc. are not to be construed as denoting or implying order or timesequences unless expressly indicated otherwise. Rather, they are to beconstrued as distinguishing two or more elements. In some embodiments,the two or more elements, although distinguishable, have the samemakeup. For example, a first memory and a second memory may indeed betwo separate memories but they both may be RAM devices that have thesame storage capacity (e.g., 4 GB).

The term “causing” or “cause” means that one or more systems (e.g.,computing devices) and/or components (e.g., processors) may in isolationor in combination with other systems and/or components bring about orhelp bring about a particular result or effect. For example, thelogistics server(s) 105 may “cause” a message to be displayed to acomputing entity 110 (e.g., via transmitting a message to the userdevice) and/or the same computing entity 110 may “cause” the samemessage to be displayed (e.g., via a processor that executesinstructions and data in a display memory of the user device).Accordingly, one or both systems may in isolation or together “cause”the effect of displaying a message.

The term “real time” includes any time frame of sufficiently shortduration as to provide reasonable response time for informationprocessing as described. Additionally, the term “real time” includeswhat is commonly termed “near real time,” generally any time frame ofsufficiently short duration as to provide reasonable response time foron-demand information processing as described (e.g., within a portion ofa second or within a few seconds). These terms, while difficult toprecisely define, are well understood by those skilled in the art.

The following embodiments represent exemplary aspects of conceptscontemplated herein. Any one of the following embodiments may becombined in a multiple dependent manner to depend from one or more otherclauses. Further, any combination of dependent embodiments (e.g.,clauses that explicitly depend from a previous clause) may be combinedwhile staying within the scope of aspects contemplated herein. Thefollowing clauses are exemplary in nature and are not limiting:

Clause 1. A system comprising: a plurality of storage units that areconfigured to receive one or more assets associated with performing oneor more shipment operations; and a conveyor apparatus that is configuredto relay the one or more assets, wherein a first asset of the one ormore assets is configured to be picked from the conveyor apparatus andloaded onto at least one storage unit of the plurality of storage unitsfor the one or more shipment operations, the conveyor apparatus beingcommunicatively coupled to the plurality of storage units orcommunicatively coupled to one or more computing devices associated withthe plurality of storage units; wherein the at least one storage unit ofthe plurality of storage units is configured to automatically rotate toa loading location at least partially in response to receiving acommunication from the conveyor apparatus or the one or more computingdevices indicating an identifier associated with the first asset.

Clause 2. The system of clause 1, wherein the plurality of storage unitsare located in a logistics vehicle, and wherein the logistics vehicle isconfigured to carry a plurality of assets associated with the one ormore shipment operations.

Clause 3. The system of clause 1, wherein the plurality of storage unitsare located on a platform adjacent to a logistics vehicle and theconveyor apparatus.

Clause 4. The system of clause 3, wherein the plurality of storage unitsare configured to be loaded into the logistics vehicle at leastpartially in response to the loading of the first asset into the atleast one storage unit.

Clause 5. The system of clause 1, further comprising a robotic armcomponent that is configured to perform the loading of the first assetinto the at least one storage unit of the plurality of storage units.

Clause 6. The system of clause 1, wherein a user operator performs theloading of the first asset into the at least one storage unit of theplurality of storage units.

Clause 7. The system of clause 1, further comprising one or more buffershelves that are configured to receive a set of assets based on the setof assets sharing a same destination location as part of a final miledelivery.

Clause 8. A conveyor apparatus comprising: a rotating component that isconfigured to cause movement of one or more assets for loading the oneor more assets into one or more storage units; a reader componentconfigured to obtain an identifier associated with the one or moreassets; and a transmitting component configured to transmit, over acomputer network, the identifier obtained by the reader component to theone or more storage units or one or more computing devices associatedwith the one or more storage units, wherein the one or more storageunits are configured to rotate to a loading location for the loading ofthe one or more assets in response to receiving the identifier.

Clause 9. The conveyor apparatus of clause 8, wherein the transmitting,over the computer network, of the identifier occurs via a wirelesscommunication link between the conveyor apparatus, a computing device,and a logistics vehicle that is configured to store the one or morestorage units.

Clause 10. The conveyor apparatus of clause 8, wherein the transmitting,over the computer network, of the identifier occurs via a wiredconnection link between the conveyor apparatus and the one or morestorage units.

Clause 11 The conveyor apparatus of clause 8, wherein the one or morestorage units are located in a logistics vehicle, and wherein thelogistics vehicle is configured to carry a plurality of assetsassociated with one or more shipment operations.

Clause 12. The conveyor apparatus of clause 8, wherein the one or morestorage units are located on a platform adjacent to a logistics vehicleand the conveyor apparatus.

Clause 13. The conveyor apparatus of clause 12, wherein the one or morestorage units are configured to be loaded into the logistics vehicle inresponse to the loading of the one or more assets into the one or morestorage units.

Clause 14. The conveyor apparatus of clause 8, wherein a roboticcomponent performs the loading of the one or more assets into the one ormore storage units.

Clause 15. A computer-implemented method comprising: obtaining anidentifier of one or more assets in response to a reader componentreading a tag associated with one or more assets as the one or moreassets traverse a conveyor apparatus; and at least partially in responseto the obtaining of the identifier, causing a storage unit of aplurality of storage units to automatically rotate to a loading locationto receive the one or more assets.

Clause 16. The method of clause 15, wherein the one or more assetsinclude a plurality of assets, the method further comprising populatinga queue data structure with the identifier and a plurality of otheridentifiers associated with other assets, the populating of the queuedata structure is at least partially indicative of an order that theplurality of assets are traversing on the conveyor apparatus; and basedon the populating, causing, in near-real time relative to the pluralityof assets traversing on the conveyor apparatus, each storage unit of theplurality of storage units to rotate to the loading location in an orderthat the identifier and identifiers are populated in the queue datastructure.

Clause 17. The method of clause 16, wherein the causing the storage unitof the plurality of storage units to automatically rotate includessending a control signal to the storage unit that rotates the storageunit to the loading location based at least in part on the identifierand the order the identifier is populated in the queue data structure.

Clause 18. The method of clause 15, wherein the plurality of storageunits are located on a platform adjacent to a logistics vehicle and theconveyor apparatus.

Clause 19. The method of clause 15, wherein the plurality of storageunits are configured to be loaded into the logistics vehicle in responseto the loading of the one or more assets into the storage unit.

Clause 20. The method of clause 15, wherein a robotic component isconfigured to perform the loading of the one or more assets into thestorage unit of the plurality of storage units.

Clause 21. The method of clause 15, wherein a user operator performs aloading of a first asset into a storage unit of the plurality of storageunits.

Clause 22. The method of clause 15, further comprising receiving, viaone or more buffer shelves, a set of assets based on the set of assetssharing a same destination location as part of a final mile delivery.

Clause 23. A system comprising: a plurality of storage units that areconfigured to receive one or more assets associated with performing oneor more shipment operations; wherein the plurality of storage units arefurther configured to be placed inside and outside of a logisticsvehicle for a loading or picking of the one or more assets; and whereinthe plurality of storage units include one or more fastening componentsthat are configured to allow the plurality of storage units to becoupled together and the one or more fastening components further allowat least a portion of the plurality of storage units to pivot about anaxis.

Clause 24. The system of clause 23, further comprising: a conveyorapparatus that is configured to relay the one or more assets, wherein afirst asset of the one or more assets is configured to be picked fromthe conveyor apparatus and loaded onto at least one storage unit of theplurality of storage units for the one or more shipment operations.

Clause 25. The system of clause 24, wherein the conveyor apparatus iscommunicatively coupled to the plurality of storage units orcommunicatively coupled to one or more computing devices associated withthe plurality of storage units, and wherein the at least one storageunit of the plurality of storage units is configured to automaticallyrotate to a loading location in response to at least partially receivinga communication from the conveyor apparatus or the one or more computingdevices indicating an identity of the first asset.

Clause 26. The system of clause 23, wherein the plurality of storageunits are configured to be loaded into the logistics vehicle in responseto the loading of a first asset into at least one storage unit.

Clause 27. The system of clause 23, further comprising a robotic armcomponent that is configured to perform the loading or picking of afirst asset into or from at least one storage unit of the plurality ofstorage units.

Clause 28. The system of clause 23, wherein a user operator performs theloading or picking of the one or more assets.

Clause 29. The system of clause 23, further comprising one or morebuffer shelves that are configured to receive a set of assets based onthe set of assets sharing a same destination location as part of a finalmile delivery.

Clause 30. The system of clause 23, further comprising a conveyorapparatus that is configured to cause movement of one or more assets forloading the one or more assets into the plurality of storage units,wherein the conveyor apparatus is further configured to obtain anidentifier of the one or more assets, and wherein the conveyor apparatusis further configured to transmit, over a computer network, theidentifier to the plurality of storage units or one or more computingdevices associated with the plurality of storage units, and wherein theplurality of storage units are configured to rotate to a loadinglocation for the loading of the one or more assets in response toreceiving the identifier.

V. Conclusion

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing description and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation, unlessdescribed otherwise.

What is claimed is:
 1. A system comprising: a plurality of storage unitsthat are configured to receive one or more assets associated withperforming one or more shipment operations; and a conveyor apparatusthat is configured to relay the one or more assets, wherein a firstasset of the one or more assets is configured to be picked from theconveyor apparatus and loaded onto at least one storage unit of theplurality of storage units for the one or more shipment operations, theconveyor apparatus being communicatively coupled to the plurality ofstorage units or communicatively coupled to one or more computingdevices associated with the plurality of storage units; wherein the atleast one storage unit of the plurality of storage units is configuredto automatically rotate to a loading location at least partially inresponse to receiving a communication from the conveyor apparatus or theone or more computing devices indicating an identifier associated withthe first asset.
 2. The system of claim 1, wherein the plurality ofstorage units are located in a logistics vehicle, and wherein thelogistics vehicle is configured to carry a plurality of assetsassociated with the one or more shipment operations.
 3. The system ofclaim 1, wherein the plurality of storage units are located on aplatform adjacent to a logistics vehicle and the conveyor apparatus. 4.The system of claim 3, wherein the plurality of storage units areconfigured to be loaded into the logistics vehicle at least partially inresponse to the loading of the first asset into the at least one storageunit.
 5. The system of claim 1, further comprising a robotic armcomponent that is configured to perform the loading of the first assetinto the at least one storage unit of the plurality of storage units. 6.The system of claim 1, wherein a user operator performs the loading ofthe first asset into the at least one storage unit of the plurality ofstorage units.
 7. The system of claim 1, further comprising one or morebuffer shelves that are configured to receive a set of assets based onthe set of assets sharing a same destination location as part of a finalmile delivery.
 8. A conveyor apparatus comprising: a rotating componentthat is configured to cause movement of one or more assets for loadingthe one or more assets into one or more storage units; a readercomponent configured to obtain an identifier of the one or more assets;and a transmitting component configured to transmit, over a computernetwork, the identifier obtained by the reader component to the one ormore storage units or one or more computing devices associated with theone or more storage units, wherein the one or more storage units areconfigured to rotate to a loading location for the loading of the one ormore assets in response to receiving the identifier.
 9. The conveyorapparatus of claim 8, wherein the transmitting, over the computernetwork, of the identifier occurs via a wireless communication linkbetween the conveyor apparatus, a computing device, and a logisticsvehicle that is configured to store the one or more storage units. 10.The conveyor apparatus of claim 8, wherein the transmitting, over thecomputer network, of the identifier occurs via a wired connection linkbetween the conveyor apparatus and the one or more storage units. 11.The conveyor apparatus of claim 8, wherein the one or more storage unitsare located in a logistics vehicle, and wherein the logistics vehicle isconfigured to carry a plurality of assets associated with one or moreshipment operations.
 12. The conveyor apparatus of claim 8, wherein theone or more storage units are located on a platform adjacent to alogistics vehicle and the conveyor apparatus.
 13. The conveyor apparatusof claim 12, wherein the one or more storage units are configured to beloaded into the logistics vehicle in response to the loading of the oneor more assets into the one or more storage units.
 14. The conveyorapparatus of claim 8, wherein a robotic component performs the loadingof the one or more assets into the one or more storage units.
 15. Acomputer-implemented method comprising: obtaining an identifier of oneor more assets in response to a reader component reading a tagassociated with one or more assets as the one or more assets traverse aconveyor apparatus; and at least partially in response to the obtainingof the identifier, causing a storage unit of a plurality of storageunits to automatically rotate to a loading location to receive the oneor more assets.
 16. The method of claim 15, wherein the one or moreassets include a plurality of assets, the method further comprisingpopulating a queue data structure with the identifier and a plurality ofother identifiers associated with other assets, the populating of thequeue data structure is at least partially indicative of an order thatthe plurality of assets are traversing on the conveyor apparatus; andbased on the populating, causing, in near-real time relative to theplurality of assets traversing on the conveyor apparatus, each storageunit of the plurality of storage units to rotate to the loading locationin an order that the identifier and identifiers are populated in thequeue data structure.
 17. The method of claim 16, wherein the causingthe storage unit of the plurality of storage units to automaticallyrotate includes sending a control signal to the storage unit thatrotates the storage unit to the loading location based at least in parton the identifier and the order the identifier is populated in the queuedata structure.
 18. The method of claim 15, wherein the plurality ofstorage units are located on a platform adjacent to a logistics vehicleand the conveyor apparatus.
 19. The method of claim 15, wherein theplurality of storage units are configured to be loaded into thelogistics vehicle in response to the loading of the one or more assetsinto the storage unit.
 20. The method of claim 15, wherein a roboticcomponent is configured to perform the loading of the one or more assetsinto the storage unit of the plurality of storage units.